You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 16, 2022. It is now read-only.
We would like users to be able to view their order/trade history without bogging down the performance of the active orderbook.
One proposed suggestion would be to move completed orders to a separate db/server and remove them from the normal order book. When users need to view their trade history, they pull off of the separate DB.
The thinking here is we don't want too much data in the normal orderbook DB as that will be hit constantly. Users don't check their trade history nearly as often, so that database could be larger as it would be hit less.
The text was updated successfully, but these errors were encountered:
JonathonDunford
changed the title
FUTURE ADDITION: Store "old" orders/trades on a separate server/db
Store "old" orders/trades on a separate server/db
Feb 10, 2018
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We would like users to be able to view their order/trade history without bogging down the performance of the active orderbook.
One proposed suggestion would be to move completed orders to a separate db/server and remove them from the normal order book. When users need to view their trade history, they pull off of the separate DB.
The thinking here is we don't want too much data in the normal orderbook DB as that will be hit constantly. Users don't check their trade history nearly as often, so that database could be larger as it would be hit less.
The text was updated successfully, but these errors were encountered: