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

Data caching #78

Open
jam231 opened this issue May 28, 2014 · 0 comments
Open

Data caching #78

jam231 opened this issue May 28, 2014 · 0 comments
Labels
performance

Comments

@jam231
Copy link
Owner

jam231 commented May 28, 2014

As of now trading server cache last transactions, best sell orders and best buy orders.
Each trading server cache these values localy (many copies).
Cache invalidation is done by sending appropiate message with new values: database -> notification hub -> trading server(s).

It'd be better (cleaner, and probably faster) to use a simple, fast, embedded KV store for caching and let notification server handle updating and trading servers reading.
@jam231 jam231 changed the title Aggressive data caching Data caching May 28, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
performance
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jam231