Connection pooling with standalone Moxi
Tue, 06/19/2012 - 01:06
Hi, I'm using the Python 'smart client' from a web application and notice when load testing that the connection setup and close times dominate the total time taken to access Couchbase. It was recommended for 1.8 that as usage grows it can be advantageous to move to client-side Moxi; http://www.couchbase.com/docs/moxi-manual-1.8/moxi-performance.html. However, this page also says the 'smart client' can be even better, and that it removes the need for Moxi? I'm unsure how the smart client removes the benefit that client-side Moxi gives you from maintaining connections to the Couchbase cluster?
In addition I am wondering if I can use CAS operations through a client-side Moxi?
Thanks,
Greig
Hi Grieg,
The python client is undergoing quite a bit of change at the moment, and the end result will have the kind of persistent connections you're looking for. The code is under review right now, actually.
I don't know that we've changed the connection handling yet though. The goal at the moment was to get the developer API correct. One option at the moment is that there is a community developed python wrapper atop libcouchbase.
It doesn't have all of the functions for 2.0 though, but the guys who did it are friends and I know they use it in production. I'll see if we can give a better timeframe.
Thanks,
Matt