How does the connection pooling in that PHP client work, and how big a connection pool do you have? Does it even have one? If you do that short burst test of yours, opening new TCP connections is a performance bottleneck, but if you have a proper connection pool and a hot system, your pool should have grown to a good size that can accomodate the load.
I haven't seen the problem you describe, but I've never used the PHP client either. I'll see if I can make a similar test using our client that uses over 150 concurrent connections. /Henrik Schröder On Thu, Sep 4, 2008 at 9:28 PM, Steve Clay <[EMAIL PROTECTED]> wrote: > > I'm trying to ab test a PHP app to compare the performance of disk cache > and memcache (client/server details at end). I realize the win32 ports are > unsupported, but any assistance would be appreciated. > > During each connection I'm only doing a single get for a 16K binary item > (some gzipped content). > > With short bursts of connections (400 concurrent requests) memcached > behaves fine (though quite a bit slower than disk reads). > > When I lengthen the test to 1000 requests and run this a few times (3 or 4 > seconds of break between), memcached stops accepting connections during the > 3rd or so run. With every 20th request I'm logging the > stats['curr_connections'] and it never gets above 150 or so. In fact, even > with no concurrency, around 800 requests in the client stops connecting and > then needs some time to breathe... > > I had identical results this morning on another XP box with similar setup. > Any ideas on how I can investigate this? Should I chalk this up to "immature > Win32 port"? > > If I set up a VM w/ Linux + memcached, will I be able to connect to it from > Windows? > > PHP 5.2.6 / Apache 2.2.9 / WinXP > PHP memcache client 2.2.4-dev R1.99 > memcached 1.2.4 Win32 beta (9/3/2008) limit 1024 connections / 64MB > http://www.splinedancer.com/memcached-win32/ > > -- > Steve Clay > http://mrclay.org/ > >
