feat: postgres investigations #364
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
PR adds capabilities for logging the size of the data-node postgres database to the parameter experiments. PR also adds experiments and notebooks for analysing the following network parameters:
market.margin.scalingFactor
network.markPriceUpdateMaximumFrequency
Param:
network.markPriceUpdateMaximumFrequency
Increasing the parameter increases database size. Current mainnet value of 5s gives a memory decrease of ~8% whilst the maximum saving is ~13%.
Param:
market.margin.scalingFactor
Two sets of values tested for mainnet:
{"search_level": 1.050, "initial_margin": 1.100, "collateral_release": 1.150}
{"search_level": 1.001, "initial_margin": 2.000, "collateral_release": 4.000}
Option 2 gives a ~3% memory saving over Option 1.
Testing
Passing all tests locally.
Breaking Changes
None
Closes
Closes #358