I'm running 4 threads. For info:
pid : 6205 uptime : 70880 time : 1214233613 version : 1.2.5 pointer_size : 64 rusage_user : 891.475713 rusage_system : 5402.761651 curr_items : 78676 total_items : 1889552 bytes : 2423033309 curr_connections : 4549 total_connections : 2036523 connection_structures : 6833 cmd_get : 155887864 cmd_set : 1889552 get_hits : 154000822 get_misses : 1887042 evictions : 1395221 bytes_read : 591384483438 bytes_written : 3296884141526 limit_maxbytes : 3246391296 threads : 4 Benja. On Mon, Jun 23, 2008 at 4:16 PM, Brian Moon <[EMAIL PROTECTED]> wrote: > Benjamin Fonze wrote: > >> Well, I'm using the cache very intensively. Doing about 1,000+ >> requests/second. Memcached seem to be running fine most of the time, but >> sometimes it just let the request hang and timeout after 1 second. With >> so many queries/second, when it hangs, it quickly makes a lot of Apache >> "waiting" and eventually completely overload the web servers. >> > > Are you running memcached threaded? If not you should. If you are, you > need more threads maybe? > > I'm now trying with one big cache on a single server, and it seems to >> run better. The Memcached server is not loaded at all. Still sometimes >> the request take 500ms or even do some timeouts. >> > > That makes less sense. Unless you just had flaky hardware. > > Is 1,000+ hits per second a lot for Memcached or is it still a normal >> usage? >> > > Yes, that is quite normal. > > > -- > > Brian Moon > Senior Developer/Engineer > ------------------------------ > When you care enough to spend the very least. > http://dealnews.com/ > >
