How stable is Membase memcached?

Aaron, you're right, we are tracking down a CPU issue. However, if you read through the forums, you'll see that even during the period of CPU spiking there is minimal effect on the traffic and response times. It's something we have not yet been able to reproduce in house, but are working to get to the bottom of it.

Also note that our software is available on Ubuntu and CentOS/Red Hat and there have been no stability or CPU issues reported there (it seems to be something with Windows).

I can certainly understand your hesitancy, and it's up to you to weigh the benefits of our software. If you like, I can work with you directly to get and test a deployment in your own environment. Feel free to reach out to me.

Thanks Aaron.

Perry

FYI - even if you go the Linux route, I'd recommend using the NorthScale product and a matching smart client (since you're using Windows, I'm assuming that'd be the Enyim one). It'll save you a lot of configuration headaches, and the management console is really neat.

We're running a 2-node development cluster on Windows 2003 (2 Hyper-V instances), and 2 Cent-OS machines on production. Haven't had any problems so far other than a few client-related quirks that have been fixed.

Thanks very much, Perry. I do have a test deployment set up at the moment.
In our configuration, we are running another server on the memcached machine, so a CPU spike might affect that other server.

Is there a way of being notified when you have reproduced/fixed this issue? We will not be deploying until Spring or Summer, 2011, so we have some time to decide.

Thanks again,
Aaron

Thanks for the info, slegay.

Aaron, I'll make a note to let you know when we've reproduced and fixed the CPU issue.

Thanks for your understanding and patience.

Perry

Thanks, much appreciated!

Please refer to the following thread:

http://forums.membase.org/thread/northscale-client-100-cpu

Make sure that your client instances are disposed. The MembaseClient has a background thread for the configuration management, and this must be stopped by disposing the client.
The easiest solution is to add the following to your Global.asax:

protected void Application_End(object sender, EventArgs e)
{
    // dispose the clients here
}
Please let us know if this does not work for you.