Memcached is an open-source project. There is nothing stopping you from
making that change yourself and using it. However, you will have a hard
time finding someone to do that feature for you for free, because quite
frankly it is highly unlikely that anyone using memcached the way it was
intended
Yo,
In a few hours (or sometime tomorrow, at this point), I'm posting the
final patch series for 1.2.7-rc for public review. They'll be up for about
a day or two before we kick off the -rc.
I've been combing my inbox for days and collecting the little odds and
ends I might've missed, along with
Hi all,
We were looking around for a lightweight mechanism for viewing
memcached stats. We ended up creating a simple, but pretty useful
tool for viewing memcached stats through a browser, which we're
calling statsproxy.
You can find the tarball and instructions for statsproxy at:
http://code.g
On Mar 24, 4:33 am, JC wrote:
> I am answering to myself ;-)
>
> Well, first, this only occurs on old suse boxes (9, 10.1), and above
> all this seems to be linked to the client rather than the server
> (targeting the same server from an ubuntu is enough to make the
> behaviour desappear) so I g
On Mar 24, 1:02 pm, Trond Norbye wrote:
> Issue:http://code.google.com/p/memcached/issues/detail?id=22
> Patch:http://github.com/trondn/memcached/commit/53180103df1bbca1292a14ef96a...
Oh, I saw this go through IRC and it made perfect sense. Thanks. :)
Issue: http://code.google.com/p/memcached/issues/detail?id=22
Patch:
http://github.com/trondn/memcached/commit/53180103df1bbca1292a14ef96aab2e6a19e13cf
Cheers,
Trond
So? It's important anyway :-)
On 24 мар, 17:28, Josef Finsel wrote:
> Optional functionality, especially optional functionality that is not a part
> of the core requirements, is the most frequently misused of all
> functionality.
>
> 2009/3/24 gf
>
>
>
>
>
> > 1. It can be _optional_ functional
Optional functionality, especially optional functionality that is not a part
of the core requirements, is the most frequently misused of all
functionality.
2009/3/24 gf
>
> 1. It can be _optional_ functionality. So people can use it at their
> own risk.
> 2. > risk of memcached performing poorly
1. It can be _optional_ functionality. So people can use it at their
own risk.
2. > risk of memcached performing poorly by having more connections
open longer.
Why? AIO allows to has thousands connections open. I'm sure, it must
be more efficient than repeats.
On 24 мар, 15:00, Josef Finsel wrot
memcached works so well because it does one thing very efficiently.
Attempting to add functionality that should go in the client increases the
risk of memcached performing poorly by having more connections open longer.
If this is to be implemented, it should be implemented in the client where
it c
On 24 мар, 07:39, Dustin wrote:
> On Mar 22, 4:20 am, gf wrote:
>
> > Hello. It would be great to add new "wait timeout" argument to the get
> > () method. If it is defined and the key doesn't exists a the moment,
> > client should wait untill the key will be added or untill the timeout
> > w
I am answering to myself ;-)
Well, first, this only occurs on old suse boxes (9, 10.1), and above
all this seems to be linked to the client rather than the server
(targeting the same server from an ubuntu is enough to make the
behaviour desappear) so I guess I have nothing to complain about the
1
12 matches
Mail list logo
