On Thu, Oct 13, 2016 at 11:32 PM, dormando <dorma...@rydia.net> wrote:

> I think this is fixed in 1.4.32. Been broken for a very long time
> unfortunately.
>

Finally getting back to this.  I'm testing with 1.4.33.  Looks good, thanks.


I'm trying to understand all the new options.  What does -o modern include?

*- modern: Enables 'modern' defaults. See release notes (highly
recommended!).*

Which release notes
<https://github.com/memcached/memcached/wiki/ReleaseNotes> should I be
looking at?

Or rather, can you provide guidance on what options to use?   We are using
Memcached as a general cache so our value sizes and set frequency varies
quite a bit.  I suspect being able to reallocate slab space would be
helpful in our case.

We also have a need to store some larger (>1MB) items, too. (for example,
-I 4m)

Thanks,



>
> On Sun, 25 Sep 2016, Bill Moseley wrote:
>
> > If I understand the documentation correctly, evicted_time should show
> the seconds since the last access for the more recently evicted item.
> >
> > I'm seeing evicted_time for our production servers, but I'm not able to
> have a value show up when testing.
> >
> > I have a slab class that can hold 10 items of the value I'm writing.
> >
> > I assume I would see an evicted_time doing this:
> >  1. write a key and read it back
> >  2. sleep 5 seconds.
> >  3. write and read 10 random keys into the slab (quicly)
> >  4. Notice that there has now been one eviction
> >  5. read from the original key and get NOT FOUND
> > I then see:
> >
> >       STAT items:32:evicted 1
> > STAT items:32:evicted_nonzero 0
> > STAT items:32:evicted_time 0
> >
> >
> > Shouldn't I see evicted_time of 5 seconds since the item evicted was
> last accessed about 5 seconds before it got evicted?
> >
> > I get the same result if I use no expires times or If I set it to, say,
> 30 seconds.
> >
> > VERSION 1.4.25
> >
> >
> > --
> > Bill Moseley
> > mose...@hank.org
> >
> > --
> >
> > ---
> > 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 memcached+unsubscr...@googlegroups.com.
> > 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 memcached+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Bill Moseley
mose...@hank.org

-- 

--- 
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 memcached+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to