metalcon
metalcon copied to clipboard
News Stream Server: Bottleneck command queue
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.
for the write optimized graphity version we can actually omit the command queue. this will be interesting to see