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.

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

News Stream Server: Bottleneck command queue #1

Open
sebschlicht opened this issue Aug 8, 2013 · 1 comment
Open

News Stream Server: Bottleneck command queue #1

sebschlicht opened this issue Aug 8, 2013 · 1 comment
Assignees
Labels

Comments

@sebschlicht
Copy link
Collaborator

Problem description

One requirement to the server due to the usage of Graphity is thread-safety.
Therefore all server requests are added to a shared thread-safe queue handled by a separate worker thread.
If this queue runs full response times will be very high.

Possible solution

Commands added to the queue should contain critical graph operations only, so that at least read requests can be handled parallel.

@renepickhardt
Copy link
Owner

for the write optimized graphity version we can actually omit the command queue. this will be interesting to see

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants