Query item age / general performance expectations
Just trialing Membase and a couple of questions have come up-
-Does the product maintain a timestamp on values? We share keyed values between servers in a web farm and the process of deserializing is an expensive one. Even pulling an object graph is expensive if it hasn't changed from what the client already has (where there is additional in-memory caching). Ideally we could pass a timestamp, HTTP if-modified-since style, and only get a return if the value has actually changed.
-What sort of single-threaded performance should I be seeing? I'm testing through the Enyim client in a .NET application, and am seeing requests capped out at seemingly miserable 2,000 / second for a simple string value (on a high end core). If I parallelize request threads I can get it up to 12,000 or so before it completely saturates 4 cores. Am I doing something wrong? This seems remarkably low.
Thank you in advance for any help anyone could provide on this. Thank you!
The product does not maintain a timestamp on values at this time.
The performance you are seeing is really low. We have tested 80000+ queries per second.
Can you please send me the following stats:
version of membase
number of nodes
memory on each node
are you using the smart client?
Have you monitored the disk write queue from the web console? What do you see?
output of /opt/membase/bin/ns_server/collect_info
dforbes,
I am working on getting an answer for you and should get back to you today.
Bhawana
Forum support is great for free but sometimes you need a guaranteed response time and dedicated resources for your questions or issues.
Consider purchasing enterprise-level support from Membase: http://www.membase.com/products-and-services/overview
Call or email "sales -at- membase -dot- com" today!