On Jul 20, 12:29 pm, Jozef Sevcik sev...@styxys.com wrote:
I'm interesting in contributing with 'my' platform, but I'm not sure:
a) is there some list of what platforms are covered right now
b) how does it work ? what should I provide if I want to contribute ?
what should I study/setup ?
On Jul 20, 11:16 pm, Clint Webb webb.cl...@gmail.com wrote:
Is there any interest in a buildbot for some older hardware?
I'm guessing not, but if there is, I have some old development servers we
use.
It's not so much an issue about the age/speed of the hardware as it
is hitting platforms
Hi Dormando,
Can you explain what you mean by expire ? You've gone into great detail
about needing it, but I don't see how explicitly expiring items is doing
you get good over letting them be evicted? Or by setting more sane
expiration times?
well, lets say I have 2 G RAM in total for
The biggest problem with expiration is that in order to locate the
item to expire we would have to look at _all_ items in the cache (we
don't link the items into a expiry list). Currently we work out of the
assumption that the future memory allocation pattern will match the
current
On 21. juli. 2009, at 13.27, Henrik Schröder wrote:
Wait, you say that if you manually find items and delete them, your
cache never really grows much and you avoid the problem. But why
don't you set short expiration times on all items from the start,
then you wouldn't have to do your
Yes, there is an idea in our group which could be helpful in
delivering the better performance and more sophisticated which reduces
the fragmentation and stuff. So, I am interested in knowing about the
code of facebook's memcached to know how they are implementing so as
to link it with the idea
Updated, please let me know if that answers your questions.
Yes, this gives now better insight how they are used (not like
daily/weekly automated system, but on demand.)
I'll check my gentoo system when I get it up'n'running if it would be
worth contributing here.
Regards,
Joonas 'kerbe'
