Hey,
Was able to authenticate with your tool:
$ pwd
/home/dormando/sasl
$ cat memcached.conf
mech_list: plain
log_level: 5
sasldb_path: /home/dormando/sasl/memcached-sasl-pwdb
$ echo testpass | saslpasswd2 -f
/home/dormando/sasl/memcached-sasl-pwdb -a memcached -c -p testuser
$ SASL_CONF_PATH
Sorry, ran out of time today. will try for earlier tomorrow
On Mon, 9 Apr 2018, Om Kale wrote:
> Hi Dormando,I was just curious to know whether you were able to reproduce the
> above
> mentioned issue?
>
> Thanks and Regards,Om Kale
>
> On Mon, Apr 9, 2018 at 12:
itself?
>
> Thanks and Regards,Om Kale
>
>
> On Mon, Apr 9, 2018 at 10:35 AM, Om Kale <omkal...@gmail.com> wrote:
> Hey Dormando,
> I do not see the memcached-sasl-pwdb created and the password added in it.
> The steps are same as above.
> Also, is there a sp
he sasl db file:
> memcached-sasl-pwdb, need to be put?
>
>
>
>
> Thanks and Regards,Om Kale
>
>
> On Fri, Apr 6, 2018 at 3:54 PM, dormando <dorma...@rydia.net> wrote:
> Read the 30 lines around where I said, not just that line.
>
> though I guess it's
Fri, 6 Apr 2018, Om Kale wrote:
> Hey Dormando,
> Ok. When I look at the 't/binary-sasl.t' and search for the section you
> mentioned,
> I see this:
>
> # Build the auth DB for testing.
>
> my $sasldb = '/tmp/test-memcached.sasldb';
>
> unlink $sasldb;
>
>
> In
d any additional info from my side.
>
> Regards,
> Om Kale
>
>
>
> On Friday, April 6, 2018 at 12:45:26 PM UTC-7, Dormando wrote:
> No secret in database means it thinks the pwdb is empty (or it can't
> load/find the pwdb).
>
> I'm not sure why offhan
No secret in database means it thinks the pwdb is empty (or it can't
load/find the pwdb).
I'm not sure why offhand.. I can try to reproduce it but won't have time
until later today.
On Fri, 6 Apr 2018, Om Kale wrote:
> Hi Dormando,
> Thanks for the quick reply. I used the environment va
On Fri, 6 Apr 2018, Om Kale wrote:
> and then try to run my client, I get the following error on the server:
>
>
> OKALE-M-33H5:memcached-1.5.7 okale$ ./memcached -S -v
> Reading configuration from:
>
> Initialized SASL.
> mech: ``SRP'' with 15 bytes of data
> SASL (severity 2): no secret in
you can save some ram.
possibly a lot of ram. which means a lot of money.
-Dormando
--
---
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 memcache
is not possible for
> now! :)
>
> Thank you,
> Alireza
>
> On Saturday, March 17, 2018 at 10:48:05 PM UTC+3:30, Dormando wrote:
> Got it.
>
> Mind if we talk through this a bit? I have a feeling you'll do okay
> without UDP.
>
> Are you
s.
>
> With regard to testing, i'd like to PoC this with the goal of doing 1M
> events/s with 1M lookups/s for enrichment.
>
> On Sat, Mar 17, 2018 at 2:58 PM, dormando <dorma...@rydia.net> wrote:
> Hey,
>
> That is exactly the use case I would expect out
not too concerned about misses since we need to back enrich/compare
> against data that has already been ingested.
>
> Thoughts?
>
> Rob
>
> On Sat, Mar 17, 2018 at 2:22 PM, dormando <dorma...@rydia.net> wrote:
> Not sure how active this list is anymore :P
>
&
it (and update it with SO_REUSEPORT
and *_mmsg under linux) but restrict responses to single packet. It can
still be useful for fire-and-forget cases (ie; spraying touch's or
fetching flag keys asynchronously), but there isn't much use for it
otherwise these days.
Thanks,
-Dormando
--
---
You
If you're treating both servers as one pool, you cannot guarantee that.
You would have to have different client instances with a subset of servers
in each, and set keys that way.
That said, this is usually a symptom of an antipattern :( What are you
trying to accomplish?
On Sat, 10 Mar 2018,
You're restarting the server to fix this?
Can you get the output of 'stats' from the server when you're in this
condition? If I had to guess you might be leaking client connections and
running it out of sockets. there's no behavioral flag to fix that.
On Tue, 6 Mar 2018, watul123 wrote:
> Hi,
>
https://github.com/memcached/memcached/wiki/ReleaseNotes156
--
---
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
Hey,
Sorry I missed a few e-mails last week...
How are the memcached clients configured? According to the log output it
doesn't look like the clients are even attempting to authenticate.
There should be log lines around "mech:" or "sasl result code:" and so
forth.
On Tue, 20 Feb 2018, Emre
Can you add an assert within client.set or asyncGet if there're any
newlines, spaces, etc in userRequest?
Sorry, missed your response last week :(
On Tue, 20 Feb 2018, Praveen wrote:
> Thanks again Dormando for your quick inputs on this issue.
>
> The protocol we are using is Te
many things can go wrong which look like this.
On Mon, 19 Feb 2018, Praveen wrote:
> Thanks Dormando for your prompt responses on this.I really appreciate it.
>
> The server running on docker is on top of alphinelinux.
> I am able to reproduce the issue in local dev environment but I
hts on this Dormando.
>
> I need to check with my team for the version in the docker container but in
> my local dev environment memcached version is 1.4.5_4_gaa7839e where the OS
> is Windows 7 and I am running my app in Eclipse.
>
> Once key1 returns wrong data then the same inc
Just out of curiosity; what version of the server are you running?
This is always an issue with your client code.
1) if you telnet directly to memcached and run "get key1", does it return
abc or 123?
2) if abc, then you might have an ordering issue or invalid characters in
your keys (\n, space,
,
-Dormando
On Tue, 13 Feb 2018, theonajim via memcached wrote:
>
> We potentially have a need for fetching remaining time left before a key
> expires from memcached. I see that mcrouter's metaget function could meet our
> needs, but it is not implemented in open source memcached. Are there pla
> Sent from my iPhone
>
> On 30 Jan 2018, at 1:20 PM, dormando <dorma...@rydia.net> wrote:
>
> >>
> >> We have two sets or pools of memcached, and would like to use mcrouter for
> >> scaling our memcached deployments as well as provide us with HA pro
>
> We have two sets or pools of memcached, and would like to use mcrouter for
> scaling our memcached deployments as well as provide us with HA protection.
> Memcached hosts in each pool should have the same data.
>
> I have setup 2 mcrouters to perform routes as well as HA protection just for
number of evictions, by protecting active items.
4+) other improvements as well.
All by default since 1.5.0. 1.5.4 is the latest as of this writing.
-Dormando
On Tue, 16 Jan 2018, farzan dalaee wrote:
> Thanks dormando for the quick response, how can I check for the overhead of
> slabs, I
&g
-f is very hard to tune. you need to actually look at what the overhead is
on each slab class.
If you want to reduce evictions the first thing you should try is the
latest version. There're a lot of changes to improve memory efficiency,
which may just fix your problem without you having to do
./autogen.sh && ./configure && make && make test
On Tue, 14 Nov 2017, Nitin Puranik wrote:
> Hi all,
> I've been studying through the memcached sources for a while now and would
> like to build right from the source code cloned from github.
>
> However, the github source tree seems to be
last_cmd 4975273
> STAT 33:addr udp6:[::]:11211
> STAT 33:state conn_read
> STAT 33:secs_since_last_cmd 4975273
> STAT 34:addr udp6:[::]:11211
> STAT 34:state conn_read
> STAT 34:secs_since_last_cmd 4975273
> STAT 35:addr udp6:[::]:11211
> STAT 35:state conn_read
>
>
>
What's the output of "stats conns" ? what's the exact version you're on?
On Mon, 6 Nov 2017, Mocking Bird wrote:
> Hi,
>
> By using `stats` command, it's showing 800 connections but netstat displays a
> few.
>
> see
> ```
> echo stats | nc localhost 11211 | grep curr_
> STAT curr_connections
platforms.
-Dormando
On Sat, 4 Nov 2017, Elsie Wahlig wrote:
> Hi!
> I wanted to request permission to use the Memcached logo in a several
> upcoming 2017 presentation and demonstration that will use or reference
> Memcached
> open source software on Qualcomm Centriq 2400 processo
.
-Dormando
On Tue, 31 Oct 2017, satoshi fujioka wrote:
>
> Thank you for your reply.
>
> That's right, I had to restart the memcached process.
>
> Release note for 1.4.20
> https://github.com/memcached/memcached/wiki/ReleaseNotes 1420
>
> I thought that I might have encountere
No idea what that is.
Do you really need something that fast (which doesn't seem to be
supported?). Thread scalability's gotten better in mainline since they did
their bench, it seems.
If you're just playing around, sorry. I'm not familiar with the thing.
On Mon, 30 Oct 2017,
Hey,
You're saying the process was just suspended and you resumed it with a
signal? Or did it crash and you had to restart it?
I don't recall any major bugs, but that version is very old (Dec 2013), so
support will be limited.
-Dormando
On Mon, 30 Oct 2017, satoshi fujioka wrote:
> Hi.
&
https://github.com/memcached/memcached/pull/274
Still experimental, but could be a big deal for people out there. Full
notes in the PR. I'll be merging it down either this weekend or the
weekend after. Give it a shot ahead of time so I get more bugs fixed ahead
of time :)
have fun,
-Dormando
ration.
>
> Thanks -
> Manish
>
> On May 11, 2017 9:30 PM, "Manish Katiyar" <mkati...@gmail.com> wrote:
>
>
> On May 11, 2017 7:27 PM, "dormando" <dorma...@rydia.net> wrote:
> They are, I'm just a bit slow, sorry!
>
>
gt; > On Aug 25, 2017, at 00:52, dormando <dorma...@rydia.net> wrote:
> >
> > Pretty sure Frank was asking about server implementations of memcached in
> > python.
> >
> > As per that, I've only ever seen people create those for eduational
> > purposes. N
erver" brought up this in the second
result:
https://github.com/jaysonsantos/python-async-memcached-server
good luck,
-Dormando
On Fri, 25 Aug 2017, Frank Wang wrote:
> Hi Dormando,
> I am just looking for one for research purposes, but I wanted one that was
> reasonably stable
https://github.com/memcached/memcached/wiki/ReleaseNotes151
couple things worth noting. for packagers, mainly test reliability should
be improved, on top of fixing some regressions from the midversion bump.
-Dormando
--
---
You received this message because you are subscribed to the Google
to be able to
work on it this year.
-Dormando
On Thu, 24 Aug 2017, Min-Zhong "John" Lu wrote:
> We use pylibmc. Fairly stable and built-in handling of multi-server key
> distribution. The disadvantage of pylibmc (and many other client libraries)
> lies
> in its dependency
Hey,
unfortunately there's no official support for memcached on windows.
On Tue, 22 Aug 2017, prashant4xc...@gmail.com wrote:
> Is the Memcache Manager is supported in Windows 64 bit systems?
> I tried getting the Memcache.exe from enyim gitHub and is working as
> expected. But wanted to know
me to get data from other server's RAM will be more than to read from
> current server's hard-disk".
> I know there is no data on current server's hard disk but just curious to
> know that will it be more or less.
>
> Really thanks in advance,
>
> On 23 July 2017 at 01
The item_global_lock had to be held when any part of the code touched the
hash table for any reason.
On Wed, 12 Jul 2017, Qinghai Liu wrote:
> Hello, everybody! I understand the new version of Memcached not uses
> item_global_lock when shifting hashtable bucket items, but the old version of
>
erformance be better if primany memcache node and
> tomcat are on same server
Having nodes on a different server is how memcached was designed to be
used.
have fun,
-Dormando
--
---
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.
I thought there were people who worked on memcached at amazon? Can you ask
them?
If you want to truly understand it you'll have to go through the sources,
unfortunately. In the github repo there're some files in doc/ that give
high level context to how the LRU works and so forth.
There's some
https://github.com/memcached/memcached/pull/289
this commit will become 1.5.0.
please yell at me if any are poorly named.
-Dormando
--
---
You received this message because you are subscribed to the Google Groups
"memcached" group.
To unsubscribe from this group and stop receiv
nfo. I'll do that.
>
> cheers,
>
> /m
>
> On Monday, July 3, 2017 at 12:34:42 PM UTC-7, Dormando wrote:
> It never actually worked in linux... support was written for solaris and
> I've never prioritized doing it in linux.
>
> You should open an issue
It never actually worked in linux... support was written for solaris and
I've never prioritized doing it in linux.
You should open an issue on the github repo so people can register
interest there; it shouldn't be too hard to do once some other stuff has
settled down.
On Mon, 3 Jul 2017, 'Mario
of the frontend code. can't get
through the TODO fast enough :(
Will put out a patch as soon as I can.
thanks,
-Dormando
On Tue, 27 Jun 2017, dan...@twistlock.com wrote:
> Hi there,
>
> My name is Daniel and i am a security researcher @Twistlock
>
> As part of my job i am looking in to vari
Would cutting the sleep time say in half
> be safe or is there a danger there?
>
> Also, I found a new memcached term I can't find a lot of info on if you'll
> indulge me- what exactly are "reflocks"?
>
> On Thursday, June 22, 2017 at 9:01:50 PM UTC-4, Dormando wrote:
has a slab page automover that's better :P
in a week I'll be flipping all this crap over to the default. Last chance
to test!
--
---
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,
s
> 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
> S
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
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:
>
aphs 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" <dorma...@rydia.net> wrote:
> Is the evictions counter increasing all the time? I
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
uesday, June 20, 2017 at 8:06:17 PM UTC-4, Dormando wrote:
> I don't really understand what queue tail is. I didn't write that page.
>
> There's the LRU tail. Which just means the least recently used item for
> that slab class.
>
> On Tue, 20 Jun 2017, r
d what it does.
>
> On Jun 20, 2017 5:25 PM, "dormando" <dorma...@rydia.net> wrote:
> On Tue, 20 Jun 2017, red 888 wrote:
>
> > This doc says something about memcached I haven't read anywhere else:
> > Which brings me to another point, item
On Tue, 20 Jun 2017, red 888 wrote:
> This doc says something about memcached I haven't read anywhere else:
> Which brings me to another point, items/chunks are not actively
> reclaimed/expired. Memached does not
> have a background thread that explicitly expires items, reclaiming used
> chunks
u need to run newer versions with modern opens to have anything more
active happen.
-Dormando
--
---
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 memcach
https://github.com/memcached/memcached/wiki/ReleaseNotes1437
With this, a reminder:
https://groups.google.com/forum/#!topic/memcached/dVCRbacA99E
would love more testers/feedback on the algorithm.
my remaining blockers for 1.5.0 are just integrating a working page mover
algo and a few minor
b rebalancer algorithm is
once of the last 2 or 3 blockers.
Thanks!
-Dormando
--
---
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...@g
Sounds cool, go ahead!
https://www.memcached.org/images/memcached_link_125.png
pre-cut logo if you hadn't found it yet.
hope the software fits your use case well enough :P
-Dormando
On Sun, 28 May 2017, Justin Israel wrote:
> Hi!
> I wanted to know if I could have permission
ise
exits.
IF the *server* is *stopping*, you must run your test with memcached under
GDB:
$ make
[etc]
$ gdb ./memcached-debug
(gdb) r -m 512 [any other start argument]
Then, once it exits, run:
(gdb) bt
No stack.
instead of "no stack", you should get a lot of output.
thanks,
Hey,
We'll need a lot more information about exactly what's happening; what
version you're using, what the exact errors you're seeing are, etc.
You might be well served by this page though:
http://memcached.org/timeouts
On Sun, 14 May 2017, Jellf Nainggolan wrote:
> Hello,
> I got issue with
Hey,
Can you describe what "going offline" means exactly? is the server
crashing, is the client disconnecting, or etc?
On Tue, 9 May 2017, rajesh pilla wrote:
> Hi Team,
> I am trying to setup Memcached(1.4.36) with SASL support. After the setup,
> when I try to start my application using
https://github.com/memcached/memcached/pull/274
take a look, send in questions/etc. it's probably still a monthish out
from merge-down.
--
---
You received this message because you are subscribed to the Google Groups
"memcached" group.
To unsubscribe from this group and stop receiving emails
That's more application level.
https://github.com/memcached/memcached/wiki/ProgrammingTricks#avoiding-stampeding-herd
On Mon, 1 May 2017, Arunav Sanyal wrote:
> Is there a configuration setting or do we have to implement our own monitor.
>
> --
>
> ---
> You received this message because you
>
>
> On Wednesday, April 26, 2017 at 11:57:43 PM UTC-7, Dormando wrote:
> Are you reusing connections, or re-SASL'ing every time? I wonder if the
> underlying sasl daemon/mechanism is failing. SASL stuff is only ever
> checked when the connection is firs
om conn_mwrite to conn_new_cmd
> 36: going from conn_new_cmd to conn_waiting
> 36: going from conn_waiting to conn_read
> 36: going from conn_read to conn_parse_cmd
> <36 Read binary protocol data:
> <36 0x80 0x07 0x00 0x00
> <36 0x00 0x00 0x00 0x00
> <36 0x
closed.
>
> Thanks again,
> Atul
>
> On Wednesday, April 26, 2017 at 10:30:14 PM UTC-7, Dormando wrote:
> Ok.
>
> The binary protocol is tested pretty well so it's *probably* something
> in
> your program, but I won't rule out a bug on the server either.
of picture completely, and spawned the memcached with
> binary protocol and still I see the the intermittent behavior.
>
> On Wednesday, April 26, 2017 at 9:54:00 PM UTC-7, Dormando wrote:
> Looks like the protocol is getting out of sync somehow.
>
> conn_waiting onl
_waiting to conn_read
> 36: going from conn_read to conn_closing
> <36 connection closed.
> 36: going from conn_closing to conn_closed
>
>
>
> On Wednesday, April 26, 2017 at 5:02:04 PM UTC-7, Dormando wrote:
> Any way to get more information about the timeout
Any way to get more information about the timeouts you're seeing?
There's nothing in the protocol that would cause "timeouts", but bugs
somewhere could cause clients to hang waiting on more data I guess.
You're sure they're timeouts and not some other kind of error?
On Wed, 26 Apr 2017, Atul
>
> No, i'm not talking about performance trouble with 63 slab classes (and I
> think I mistook that -- it should be 62 per PR 97). I'm talking about that in
> old versions when we could have two hundred classes, which I believed could
> result in memory inefficiency.
>
> (and in old versions if
can also be bugs. The code's had a few rounds of work and gets a lot
of bench testing but it's still relatively new. I do try very hard to not
have bugs.
As it matures, I might lower the default max class to 256k or even 128k,
but I don't recommend trying that right now. Benefit would be get
to gather
anyway :(
Under-utilization of memory isn't a problem per se, unless you're not
getting as much benefit as you potentially could :)
-Dormando
On Wed, 26 Apr 2017, Min-Zhong "John" Lu wrote:
> Well I must be doomed and I feel embarrassed now.
> TL;DR: It's an error on my si
Hey,
That's still missing some information. How is the daemon itself
exiting/crashing/etc? I need at least a small hint to go on.
thanks,
-Dormando
On Tue, 25 Apr 2017, seenivasan g wrote:
> Hello Dormando,
> Thanks for the response.
>
> Note: We are running memcached on non-root
Hey,
Can you provide any information on the crash itself? Any segfault lines in
dmesg, prints/abort lines from the daemon, or ideally a backtrace from a
core file?
thanks,
-Dormando
On Tue, 25 Apr 2017, Jack2498 wrote:
> Hello Team,
> I have followed these steps to compile & Instanc
le days and a few days later I'll ping back on whether I'm still seeing
> the
> failures.
>
> I'm attaching |stats items| here. Also attaching those |stats| and |stats
> slabs|
> dumped at the same time for consistency.
>
> Will come back with more info for the fun,
> - Mnjul
(the same as
item size max). Would be great to know if this makes the problem go away,
since it means I have some more stuff to tune there.
have fun,
-Dormando
On Mon, 24 Apr 2017, Min-Zhong "John" Lu wrote:
> Hi there,
>
> I've recently been investigating an intermittent &
Hmmm...
Not sure who if anyone maintains libmemcached anymore. Need to look into
it somehow.
On Wed, 19 Apr 2017, Balázs Hinel wrote:
> Hi,
> I haven't found anything on this mailing list about this issue:
>
> https://bugs.gentoo.org/show_bug.cgi?id=579934
>
Are there any more details as to how you're doing this? If you have to
iterate every item in the cache to delete a tag your performance may be
even worse than you're expecting.
On Wed, 22 Mar 2017, Volodymyr Volynets wrote:
> Hi,
> I am working on adding tags to and was able to receive and store
run all of the test scenarios for long enough before the last
release to catch it.
Was being more careful with this chunk fix because it had a few bugs that
took some hammering to find to begin with.
have fun,
-Dormando
--
---
You received this message because you are subscribed to the Google
Hi,
memcached_clone is probably always necessary if you've created the
structures in one process and then use them in another. It's definitely
required if you're using the instance in both processes. However, even
with a single process you still have complications when processes exit or
hit other
https://github.com/memcached/memcached/wiki/ReleaseNotes1435
Try out these hit ratio fixes. :)
--
---
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
mansfi...@netflix.com
> K: {M: mobile, E: email, K: key}
> }
>
> On Wed, Jan 25, 2017 at 11:33 AM, dormando <dorma...@rydia.net> wrote:
> Okay, so it's the big rollup that gets delayed. Makes sense.
>
> You're using binary protocol for everything? That's a m
), but
> having a dynamic setting would have lowered the operational complexity of the
> tuning.
>
>
> Scott Mansfield
> Product > Consumer Science Eng > EVCache > Sr. Software Eng
> {
> M: 352-514-9452
> E: smansfi...@netflix.com
> K: {M: mobile, E: ema
ood idea to dynamically change that. It
> might cause unexpected
> behavior if one bad client sends huge requests.
>
>
> Scott Mansfield
> Product > Consumer Science Eng > EVCache > Sr. Software Eng
> {
> M: 352-514-9452
> E: smansfi...@netflix.com
>
M
> To: memcached <memcached@googlegroups.com>
> Cc: Ravikiran Gummaluri <rgum...@xilinx.com>; Venkata Ravi Shankar
> Jonnalagadda
> <vjon...@xilinx.com>; Sunita Jain <suni...@xilinx.com>
> Subject: Re: Ordering of commands per connection
>
it a
proof of concept or some kind of a product?
have fun,
-Dormando
On Mon, 23 Jan 2017, Ravi Kiran wrote:
> HI ,
> We are planning to use the MemchaheD software and accelerate it with hardware
> offload. We would like to know
> from protocol prospective each connection should maint
You'll have to ask amazon. that's a fork and I don't support it.
On Fri, 13 Jan 2017, Smith Hua wrote:
> We used aws elastic cache, the latest is 1.4.24, is this version be good to
> enable auto move?
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
>
The latest version is 1.4.34. .24 is 1.5 years old.
On Fri, 13 Jan 2017, Smith Hua wrote:
> Is 1.4.24 belongs to your mentioned old version?
>
> On Friday, January 13, 2017 at 8:37:19 AM UTC, Dormando wrote:
> No.
>
> Though the automover isn't very good in that o
No.
Though the automover isn't very good in that old version. Better in the
latest ones (`-o modern` has a lot of tricks overall)
On Fri, 13 Jan 2017, Smith Hua wrote:
> Hi
> I want to know if enable Slab Reassign and AutoMove will impact memcached
> performance, if impact, will the impact
visible on multigets)
if anyone wants to try/poke/test each or a combination of these branches.
going to let them bake a little while in case I think of anything else to
add. They're mostly done though.
have fun,
-Dormando
--
---
You received this message because you are subscribed
https://github.com/memcached/memcached/pull/243
Could lower CPU usage/latency a tad if you make use of multigets.
Otherwise, syscalls probably still use overwhelming CPU :)
--
---
You received this message because you are subscribed to the Google Groups
"memcached" group.
To unsubscribe from
in the next release. If anyone can
test a bit I'd be thankful.
Also, lots of bugfixes in this release:
https://github.com/memcached/memcached/wiki/ReleaseNotes1434
have fun,
-Dormando
--
---
You received this message because you are subscribed to the Google Groups
"memcached&q
server so it
> flushes itself.
>
> On 8 December 2016 at 21:31, dormando <dorma...@rydia.net> wrote:
> One of the libraries is calling a flush command somewhere for some
> reason.
> I've no idea why it would do that offhand.
>
> You can flatly disab
is called "flush_all" if that helps.
On Thu, 8 Dec 2016, Nicolaas Thiemen Francken wrote:
> ok, but how am I doing this? how can I change this?
>
> On 8 December 2016 at 21:26, dormando <dorma...@rydia.net> wrote:
> STAT cmd_flush 19612
>
> yo
The expirey isn't inside the item value. It's part of the protocol when
storing the item. It's not in the server configuration, it's in the
*client* making the actual store.
ie: You have your serialized blob ($data), and then you want to store it
into memcached, you make a call that looks like:
You're setting the TTL to 30, not 6000. Exactly as I responded before.
In the stats you posted, you see that *evictions* are zero, but *reclaims*
are nonzero. reclaims happen when expires items are reclaimed into the
free pool.
I don't know how you're setting the TTL wrong. PHP people can
201 - 300 of 993 matches
Mail list logo
