hi, all,
I read memcached and wrote a chinese summary of memcached,
http://www.hetaoblog.com/缓存学习-memcached基本概念
do you think this is useful and fine? if you think this is useful and
ok fine,
how about adding this to the project website so that this can help
more chinese learning memcacached.
ho
Comment #8 on issue 202 by neil.mck...@gmail.com: TOP_KEYS feature fixes
http://code.google.com/p/memcached/issues/detail?id=202
OK! When you have a moment please try this:
https://github.com/sflow-nhm/memcached
./configure --enable-sflow
I forked from the "engine" branch, and added sFlow s
total_items = active + expired + deleted items
On 4月23日, 下午3时10分, eric wrote:
> hello,everyone
> i got pauzzled by the curr items and total items. as the
> memcached list said:
>
> curr_items = total number of items currently in memcache
> total_items = total number of items that have passe
> We're getting this error sometimes on a memcache call in php on
> memcache->get( "some key" );
>
> PHP Notice: Memcache::get() memcache.get:
> Server 192.168.100.53 (tcp 11211) failed with: (null) (0)
>
> And I can't find anything online about this error. Is this a time out
> or what's going on h
haahhaahahah
2011/5/19 dormando :
>> hum, if this line is ok, why the next
>> 8, shouldn´t be 9? or log_seven?
>>
>>
>> && ./mc_conn_tester.pl memcached-host:11211 5000 4 > log_three_seconds
>> && ./mc_conn_tester.pl memcached-host:11211 5000 8 > log_eight_seconds
>
> That should be seven, but odd
> hum, if this line is ok, why the next
> 8, shouldn´t be 9? or log_seven?
>
>
> && ./mc_conn_tester.pl memcached-host:11211 5000 4 > log_three_seconds
> && ./mc_conn_tester.pl memcached-host:11211 5000 8 > log_eight_seconds
That should be seven, but odd numbers bother my OCD.
hum, if this line is ok, why the next
8, shouldn´t be 9? or log_seven?
&& ./mc_conn_tester.pl memcached-host:11211 5000 4 > log_three_seconds
&& ./mc_conn_tester.pl memcached-host:11211 5000 8 > log_eight_seconds
2011/5/19 dormando :
>> nice dormando, could you check if this line is ok in your
Hi!
On May 5, 2011, at 4:20 PM, Offspring2099 wrote:
> The problem I ran into was how to keep the server list homogeneous,
> which leads into "where to store server list"? I've seen a few
If your client is based on libmemcached you can specify a file that it will
load. Currently the only strat
> nice dormando, could you check if this line is ok in your link and if
> not correct it?
>
>
> && ./mc_conn_tester.pl memcached-host:11211 5000 4 > log_three_seconds
>
> 5000 4 > log_three?
> 4 != three
>
> hehehe, maybe should be 3 > log_three or
> 4 > log_four
>
> right?
> thanks nice guide
Tha
nice dormando, could you check if this line is ok in your link and if
not correct it?
&& ./mc_conn_tester.pl memcached-host:11211 5000 4 > log_three_seconds
5000 4 > log_three?
4 != three
hehehe, maybe should be 3 > log_three or
4 > log_four
right?
thanks nice guide
2011/5/19 dormando :
>>
> Hi all,
>
> I'm encountered an issue with the Cache::Memcached client where I
> occasionally experience slowness due to timeout on the select() call. By
> default,
> Cache::Memcached has an undocumented select_timeout parameter, which
> specifies the timeout duration, which I'm currently hitt
hum, you can decrease this value and test without big problems, maybe
in a slow network 1 second for cache return some value is good... but
in a fast (100/1000mbits) you could use smaller values, must check if
your select functino allow less than 1 second (integer part), and a
miliseccond part (dec
The slowness is due calls to select(), which times out (timeout value
is set to 1 second). We're running on mod_perl. Each apache child
has its own client, and I've made it so it only runs a single child,
so it should only be a single client.
On May 19, 1:26 pm, Roberto Spadim wrote:
> hum, i t
hum, i think it´s the timeout parameter of select() function
what king of slowness? only one client? many clients?
2011/5/19 trollybaz :
> Hi all,
>
> I'm encountered an issue with the Cache::Memcached client where I
> occasionally experience slowness due to timeout on the select() call. By
> def
Hi all,
I'm encountered an issue with the Cache::Memcached client where I
occasionally experience slowness due to timeout on the select() call. By
default, Cache::Memcached has an undocumented select_timeout parameter,
which specifies the timeout duration, which I'm currently hitting
sporadic
15 matches
Mail list logo
