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!