I forgot to mention that my servers traffic output screams upwards to 80MB per second, which seems kind of steep? Could it be the binary protocol since I am passing in a new binary factory for each client instance created on my client machines?
On Sun, Feb 20, 2011 at 11:22 AM, Patrick Santora <[email protected]>wrote: > @Paul: > They are 4 core systems, so it looks like i should push it down to 4, which > I will do now :) > > The rest of the information I believe you are looking for can be found > within the stats dump below. > > @dormando: > Ok, I will push it to 4 and see what happens > > Queries a second are I believe around 16 to 20. > > Version: 1.4.5 > > Here are my current stats output, but right now the issue is not occurring. > I will have to toss out a post once it happens again. > stats > STAT pid 22821 > STAT uptime 10416 > STAT time 1298229426 > STAT version 1.4.5 > STAT pointer_size 64 > STAT rusage_user 32.524055 > STAT rusage_system 121.877471 > STAT curr_connections 843 > STAT total_connections 1312 > STAT connection_structures 904 > STAT cmd_get 196833 > STAT cmd_set 19566 > STAT cmd_flush 0 > STAT get_hits 192557 > STAT get_misses 4276 > STAT delete_misses 0 > STAT delete_hits 0 > STAT incr_misses 0 > STAT incr_hits 0 > STAT decr_misses 0 > STAT decr_hits 0 > STAT cas_misses 0 > STAT cas_hits 0 > STAT cas_badval 0 > STAT auth_cmds 0 > STAT auth_errors 0 > STAT bytes_read 1466964195 > STAT bytes_written 15148562971 > STAT limit_maxbytes 536870912 > STAT accepting_conns 1 > STAT listen_disabled_num 0 > STAT threads 20 > STAT conn_yields 0 > STAT bytes 2532172 > STAT curr_items 2657 > STAT total_items 19566 > STAT evictions 0 > STAT reclaimed 4801 > END > > Thanks! > > > On Sun, Feb 20, 2011 at 10:55 AM, dormando <[email protected]> wrote: > >> > What I am seeing is that when my memcached container hits around 10MB >> > of written traffic is starts to bottleneck causing my front end >> > systems to slow WAY down. I've turned on verbose debugging and see no >> > issues and there are no complaints on the front end stating that the >> > connection clients are not able to hit memcached. >> > >> > Has anyone seen anything like this before? >> > >> > I would appreciate any feedback that could help out with this. >> >> Lower the threads down to 4 or 8 or so. It's rare that it needs adjusting. >> >> Things we'd like to know: >> >> - your version of memcached >> - how many queries/second you run >> - stats output usually helps >> >> have you gone through this page yet? >> http://code.google.com/p/memcached/wiki/Timeouts >> then there's this: >> http://code.google.com/p/memcached/wiki/NewServerMaint >> >> >> >
