How would one go about managing multiple memcached instances on the
same server for startup/shutdown and restarts ?
Currently have 2x load balanced web servers each with one memcached
instance using /etc/init.d/memcached, /usr/local/bin/start-memcached
and memcached.conf approach but this isn't se
On Feb 10, 5:27 pm, Henrik Schröder wrote:
> I could probably add the above to the project, but then you would have to
> convince me that there's a legitimate usecase for noreply. :-)
It's not just use cases, it's bugs. There are times when a response
might come back even though the client in
Hm, adding support for noreply shouldn't be that hard, you could probably
hack it in yourself:
On line 343 in Memcached.cs, add a parameter to the private store method,
"bool quiet" or something, add "noreply" to the commandlines if it's true,
and then change the return statement on line 383 to "r
I would definitely stay away from that java port if I were you, unless it's
been updated recently. The whole reason for us writing the BeITMemcached
client in the first place was that we were using the java port, but it would
suddenly start throwing lots and lots of errors. When we tried to underst
I'm maintaining that one, although since it just works fine there hasn't
been much to do with it lately. I should get around to implementing the
binary protocol sometime, but so far I haven't had the time or the need to
do so, and the lack of a proper windows version of the server makes it even
les
On Wed, Feb 10, 2010 at 23:04, tachu wrote:
> will this
> slow down a lot of the key hashing part of memcache
No, the naive server selection is O(1), the consistent hash server selection
is O(log(n))
as well as the
> initialization of the client when we loop to add servers..
>
That depends, t
On Feb 10, 2:37 pm, Jeremy Dunck wrote:
> I'm looking for a .Net client that's actively maintained, preferably
> with noreply support.
What is your goal with noreply?
If you're having a performance problem you hope to solve with it,
you're better off with binary protocol and quiet comma
hi
yeah, no new commits, mostly because it "just works" :)
no reply is not supported yet, but will be soon (tm), and i'm working on the
binary protocol as well
additionally, i'm moving away from codeplex to github:
http://github.com/enyim/EnyimMemcached
a.
On Feb 10, 2010, at 11:57 PM, Pe
I've been in touch with the Enyim developer directly, sounds like he's still
actively engaged with the project even if there haven't been any major
updates as of late.
There's also a client maintained within Sourceforge:
http://sourceforge.net/projects/memcacheddotnet/
On Wed, Feb 10, 2010 at 2:5
Enyim, but I'm not sure about noreply.
http://enyimmemcached.codeplex.com/
However, there seems to be last commit from Dec 2008
On 10 February 2010 23:37, Jeremy Dunck wrote:
> I'm looking for a .Net client that's actively maintained, preferably
> with noreply support.
>
> This one looks to be m
I'm looking for a .Net client that's actively maintained, preferably
with noreply support.
This one looks to be maintained: http://code.google.com/p/beitmemcached/
Did I miss any others?
BeITmemcached doesn't seem to support noreply.
Thanks!
I've been lately running into some limitation using memcache and ec2.
Given that this is a EC2 issue i might get flamed but I was hoping to
get opinion from people here that have been using memcache. We
currently run a cluster of aproximately 40 memcache servers with about
6.5 gb of ram each machin
I just happened to bump up one of my boxes to latest Cache::Memcached
version from CPAN and noticed that it breaks unix domain socket support - or
rather, dumps a warning. Here's a fix - it just moves some udp/tcp specific
code into the non-unixdomain code block.
Technically, to resolve this warni
13 matches
Mail list logo
