The expiration for all items is 30 mins

=================== stats ==================================
STAT pid 1
STAT uptime 874624
STAT time 1498177737
STAT version 1.4.34
STAT libevent 2.0.21-stable
STAT pointer_size 64
STAT rusage_user 149928.880000
STAT rusage_system 20235.240000
STAT curr_connections 342
STAT total_connections 14816
STAT rejected_connections 0
STAT connection_structures 344
STAT reserved_fds 10
STAT cmd_get 2431931655
STAT cmd_set 1674656279
STAT cmd_flush 0
STAT cmd_touch 0
STAT cmd_config_get 109145
STAT cmd_config_set 2
STAT get_hits 1737530329
STAT get_misses 694401326
STAT get_expired 49107
STAT get_flushed 0
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 4
STAT cas_hits 451106648
STAT cas_badval 530100
STAT touch_hits 0
STAT touch_misses 0
STAT auth_cmds 0
STAT auth_errors 0
STAT bytes_read 1319246358299
STAT bytes_written 1238308983641
STAT limit_maxbytes 6787432448
STAT launch_time_maxbytes 6787432448
STAT accepting_conns 1
STAT listen_disabled_num 0
STAT time_in_listen_disabled_us 0
STAT threads 2
STAT conn_yields 0
STAT hash_power_level 22
STAT hash_bytes 33554432
STAT hash_is_expanding 0
STAT curr_config 1
STAT slab_reassign_rescues 0
STAT slab_reassign_chunk_rescues 0
STAT slab_reassign_evictions_nomem 0
STAT slab_reassign_inline_reclaim 0
STAT slab_reassign_busy_items 0
STAT slab_reassign_running 0
STAT slabs_moved 0
STAT lru_crawler_running 0
STAT lru_crawler_starts 629012
STAT lru_maintainer_juggles 513869396
STAT malloc_fails 0
STAT log_worker_dropped 0
STAT log_worker_written 0
STAT log_watcher_skipped 0
STAT log_watcher_sent 0
STAT bytes 2520842198
STAT curr_items 2234247
STAT total_items 1674126175
STAT expired_unfetched 48225226
STAT evicted_unfetched 0
STAT evicted_active 0
STAT evictions 0
STAT reclaimed 447052919
STAT crawler_reclaimed 437349953
STAT crawler_items_checked 217893516538
STAT lrutail_reflocked 12575
STAT moves_to_cold 916002463
STAT moves_to_warm 143197938
STAT moves_within_lru 655572218
STAT direct_reclaims 0

==================================== stats settings 
=================================================
stats settings
STAT maxbytes 6787432448
STAT launch_time_maxbytes 6787432448
STAT maxconns 65000
STAT tcpport 11211
STAT udpport 11211
STAT inter NULL
STAT verbosity 1
STAT oldest 0
STAT evictions on
STAT domain_socket NULL
STAT umask 700
STAT growth_factor 1.15
STAT chunk_size 5
STAT num_threads 2
STAT num_threads_per_udp 2
STAT stat_key_prefix :
STAT detail_enabled no
STAT reqs_per_event 20
STAT cas_enabled yes
STAT tcp_backlog 1024
STAT binding_protocol auto-negotiate
STAT auth_enabled_sasl no
STAT item_size_max 1048576
STAT config_max 16
STAT config_size_max 65536
STAT maxconns_fast yes
STAT hashpower_init 16
STAT slab_reassign yes
STAT slab_automove 0
STAT slab_chunk_max 524288
STAT lru_crawler yes
STAT lru_crawler_sleep 100
STAT lru_crawler_tocrawl 0
STAT tail_repair_time 0
STAT flush_enabled yes
STAT dump_enabled yes
STAT hash_algorithm murmur3
STAT lru_maintainer_thread yes
STAT hot_lru_pct 32
STAT warm_lru_pct 32
STAT expirezero_does_not_evict no
STAT idle_timeout 0
STAT watcher_logbuf_size 262144
STAT worker_logbuf_size 65536
STAT track_sizes no




On Thursday, June 22, 2017 at 7:53:56 PM UTC-4, Dormando wrote:
>
> Can you paste the full output from the 'stats' command against the server? 
> Also: "stats settings" would be great. 
>
> Also; do you know anything about your data? what the TTL's are, for 
> instance? It's possible a bunch of stuff expires, which can get reclaimed 
> quickly by some processes depending on your start arguments. 
>
> On Thu, 22 Jun 2017, red 888 wrote: 
>
> > Oh sorry! Version 1.4.34. 
> > 
> > On Thursday, June 22, 2017 at 4:52:18 PM UTC-4, Dormando wrote: 
> >       Think I've asked this a few times; what version are you running? 
> > 
> >       On Thu, 22 Jun 2017, red 888 wrote: 
> > 
> >       > So when I look at my stats I see no cmd_flush commands are being 
> run. cmd_flush is 0 
> >       and stays at 0. 
> >       > 
> >       > On Thursday, June 22, 2017 at 12:44:28 PM UTC-4, Dormando wrote: 
> >       >       Looks like a weird access pattern. you're filling memory, 
> evicting a bit, 
> >       >       then losing all of it at once. Is your "cmd_flush" counter 
> increasing? 
> >       > 
> >       >       On Thu, 22 Jun 2017, red 888 wrote: 
> >       > 
> >       >       > If I look at the slab stats over time I see the % of 
> chunks_used (relative to 
> >       >       total_chunks) spike up (some slab classes hit 45% some hit 
> 75%) then spike 
> >       >       > down and at the same time they are spiking down 
> evictions spike up. This 
> >       happens about 
> >       >       every 2-4 minutes. 
> >       >       > 
> >       >       > I've attached a screen shot of this pattern in a time 
> series (raw stats not 
> >       >       phpmemchacheadmin). In the graphs I'm filtering for just 
> one slab class but I 
> >       >       > see this for all the most active slabs ( roughly 5 
> active slab classes). 
> >       >       > Inline image 2 
> >       >       > 
> >       >       > On Jun 21, 2017 2:27 PM, "dormando" <[email protected]> 
> wrote: 
> >       >       >       Is the evictions counter increasing all the time? 
> It might only be 
> >       >       >       completely full sometimes, which would cause 
> evictions (like during 
> >       peak). 
> >       >       > 
> >       >       >       if used is less than total but evictions is going 
> up, either you have an 
> >       >       >       old broken version of memcached or that 
> phpmemcachedadmin thing is wrong, 
> >       >       >       and you should just look at the output of the 
> "stats items" and "stats 
> >       >       >       slabs" commands. 
> >       >       > 
> >       >       >       On Wed, 21 Jun 2017, red 888 wrote: 
> >       >       > 
> >       >       >       > Here is a snap shot of one of my slab class's 
> stats (from 
> >       PHPMemcachedAdmin): 
> >       >       >       > 
> >       >       >       > [Capture.PNG] 
> >       >       >       > 
> >       >       >       > 
> >       >       >       > So what I'm confused about is why, with my 
> used_chunks so low, am I 
> >       getting 
> >       >       evictions for this slab class? 
> >       >       >       > 
> >       >       >       > 
> >       >       >       > used_chunks are chunks with items that have not 
> expired yet and 
> >       total_chunks is 
> >       >       all allocated chunks including chunks with items that 
> >       >       >       _have_ expired 
> >       >       >       > correct? 
> >       >       >       > 
> >       >       >       > 
> >       >       >       > If thats the case it means if 25% of the 
> allocated chunks are "used" 
> >       and 75% of 
> >       >       the allocated chunks have expired. So it should have 
> plenty 
> >       >       >       of chunks to 
> >       >       >       > reclaim before having to evict I would think. 
> >       >       >       > 
> >       >       >       > 
> >       >       >       > 
> >       >       >       > -- 
> >       >       >       > 
> >       >       >       > --- 
> >       >       >       > You received this message because you are 
> subscribed to the Google 
> >       Groups 
> >       >       "memcached" group. 
> >       >       >       > To unsubscribe from this group and stop 
> receiving emails from it, send 
> >       an email 
> >       >       to [email protected]. 
> >       >       >       > For more options, visit 
> https://groups.google.com/d/optout. 
> >       >       >       > 
> >       >       >       > 
> >       >       > 
> >       >       >       -- 
> >       >       > 
> >       >       >       --- 
> >       >       >       You received this message because you are 
> subscribed to a topic in the 
> >       Google 
> >       >       Groups "memcached" group. 
> >       >       >       To unsubscribe from this topic, visit 
> >       >       
> https://groups.google.com/d/topic/memcached/VXm-hnGzqXY/unsubscribe. 
> >       >       >       To unsubscribe from this group and all its topics, 
> send an email to 
> >       >       [email protected]. 
> >       >       >       For more options, visit 
> https://groups.google.com/d/optout. 
> >       >       > 
> >       >       > -- 
> >       >       > 
> >       >       > --- 
> >       >       > You received this message because you are subscribed to 
> the Google Groups 
> >       "memcached" 
> >       >       group. 
> >       >       > To unsubscribe from this group and stop receiving emails 
> from it, send an email 
> >       to 
> >       >       [email protected]. 
> >       >       > For more options, visit 
> https://groups.google.com/d/optout. 
> >       >       > 
> >       >       > 
> >       > 
> >       > -- 
> >       > 
> >       > --- 
> >       > You received this message because you are subscribed to the 
> Google Groups "memcached" 
> >       group. 
> >       > To unsubscribe from this group and stop receiving emails from 
> it, send an email to 
> >       > [email protected]. 
> >       > For more options, visit https://groups.google.com/d/optout. 
> >       > 
> >       > 
> > 
> > -- 
> > 
> > --- 
> > You received this message because you are subscribed to the Google 
> Groups "memcached" group. 
> > To unsubscribe from this group and stop receiving emails from it, send 
> an email to 
> > [email protected] <javascript:>. 
> > For more options, visit https://groups.google.com/d/optout. 
> > 
> >

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"memcached" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to