On Jul 20, 2007, at 2:19 PM, Andrew B. Westmoreland wrote:
[....]
Whereas a simple "select a from b where primary key ='x' " was
taking ~300ms to get from our database over a simple (and very
busy) GigE switch, the memcache is running on localhost and is
seeing "query" times more like ~600ms.
We tested it on many batch runs, and it seems that using the
memcache (as configured) causes a performance hit of approximately
20%. This is for a CPU-bound process that uses 100% of all CPU
cores in both testing scenarios.
Did you try putting memcached on another host with free CPU?
(Is the 300 vs 600ms *per db/memcached query* ?!)
- ask
--
http://develooper.com/ - http://askask.com/
