Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Use fuzzing run setup to investigate data-node database size with different margin settings and separated different mark price frequency #358

Open
davidsiska-vega opened this issue Mar 17, 2023 · 1 comment · May be fixed by #364
Open

Use fuzzing run setup to investigate data-node database size with different margin settings and separated different mark price frequency #358

davidsiska-vega opened this issue Mar 17, 2023 · 1 comment · May be fixed by #364

Comments

@davidsiska-vega
Copy link
Contributor

davidsiska-vega commented Mar 17, 2023 •
edited
Loading

Run the fuzzing run on a sufficiently long running market (at least 24h null-chain time and a good number orders / second on average) under two identical scenarios except:

  1. margin scaling levels are (search, initial, release) = (1.050, 1.100, 1.150)
  2. margin scaling levels are (search, initial, release) = (1.001, 2.000, 4.000).

The aim would be to run this, settle the markets, make sure that data node is caught up and then compare the size of the Postgres database in each case.

Run a separate experiment where you vary the mark price frequency:

  1. mark price update frequency 2s, 10s, 30s, 60s.
@davidsiska-vega
Copy link
Contributor Author

We should use the same price sequence (same random seed when generating) in both cases.

@davidsiska-vega davidsiska-vega changed the title Use fuzzing run setup to investigate data-node database size with different margin settings Use fuzzing run setup to investigate data-node database size with different margin settings and separated different mark price frequency Mar 21, 2023
@cdummett cdummett linked a pull request Mar 21, 2023 that will close this issue
Draft
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat: postgres investigations vegaprotocol/vega-market-sim
1 participant
@davidsiska-vega