/memcached, High-performance distributed memory object caching system
1.4.20nb2, Package name:
memcached-1.4.20nb2, Maintainer: pkgsrc-users
memcached is a high-performance, distributed memory object caching
system, generic in nature, but intended for use in speeding up dynamic
web applications by alleviating database load.
Master sites: SHA1:
Version history: (Expand)
- (2014-07-16) Updated to version: memcached-1.4.20nb2
- (2014-05-30) Updated to version: memcached-1.4.20nb1
- (2014-05-18) Updated to version: memcached-1.4.20
- (2014-05-04) Updated to version: memcached-1.4.19
- (2014-04-30) Updated to version: memcached-1.4.18nb1
- (2014-04-25) Updated to version: memcached-1.4.18
CVS history: (Expand)
| 2014-07-15 19:30:26 by Filip Hajny | Files touched by this commit (3) |
Fix my previous commit, use user/group vars properly.
| 2014-07-15 18:52:34 by Thomas Klausner | Files touched by this commit (1) |
Set PKG_HOME, which is used but not set.
XXX: please check if this is what was intended here.
| 2014-07-15 16:28:26 by Filip Hajny | Files touched by this commit (1) | |
Fix invalid PKG_USERS usage. Clean up unneeded bits. Bump PKGREVISION.
| 2014-05-30 01:38:20 by Thomas Klausner | Files touched by this commit (3049) |
Bump for perl-5.20.0.
Do it for all packages that
* mention perl, or
* have a directory name starting with p5-*, or
* depend on a package starting with p5-
like last time, for 5.18, where this didn't lead to complaints.
Let me know if you have any this time.
| 2014-05-18 10:15:17 by Thomas Klausner | Files touched by this commit (2) | |
Update to 1.4.20:
Just one tiny change to fix a regression causing threads to lock
up and spin max CPU.
1.4.18 and 1.4.19 were affected. 1.4.17 and earlier were not
affected. If you are on .18 or .19 an upgrade to 1.4.20 is strongly
Thanks to commando.io for reporting the bug initially and putting
up with me being blind for a few weeks.
Fix a race condition causing new connections to appear closed,
causing an inifinte loop.
| 2014-05-04 19:04:48 by Thomas Klausner | Files touched by this commit (2) | |
Update to 1.4.19:
Fix endianness detection during configure.
Fixes a performance regression with binary protocol (up to 20%)
Fix rare segfault in incr/decr.
disable tail_repair_time by default.
Likely not needed anymore, and can rarely cause bugs.
use the right hashpower for the item_locks table. Small perf improvement.
Fix crash for LRU crawler while using lock elision (haswell+ processors)
| 2014-04-30 07:39:19 by Blue Rats | Files touched by this commit (3) | |
Make rc.d init script work more like www/spawn-fcgi to facilitate the
execution of multiple memcached instances. Create home directory in
VARBASE/chroot/memcached for these PID files. Add MESSAGE to explain usage
to user. Usage is simple - set the following in rc.conf:
memcached_jobs="job0 ... jobN"
memcached_job0_args="-p 11211 -m 64 -c 1024"
memcached_jobN_args="-p 1121N -m 64 -c 1024"
| 2014-04-25 11:27:37 by Thomas Klausner | Files touched by this commit (5) | |
Update to 1.4.18:
New "stats conns" command, which will show you what currently open
connections are up to, how idle they've been, etc. Starttime Hash
The jenkins hash was getting a little long in the tooth, and we
might want to add specific hash algorithms for different platforms
in the future. This makes it selectable in some sense. We've
initially added murmur3 hash to the lineup and that seems to run
a tiny bit faster in some tests.
-o hash_algorithm=murmur3 LRU Crawler
A new background thread emerges! Currently experimental, so the
syntax might change. If you run into bugs please let us know (though
it's been testing fine in torture tests so far).
If you wish to clean your slab classes of items which have been
expired, either one-time or periodically, this will do it with low
impact as a background operation.
Currently it requires kicking off a crawl via manual command:
First, enable the thread: lru_crawler enable or use -o lru_crawler
as a starttime option.
lru_crawler crawl 1,3,5
... would crawl slab classes 1,3,5 looking for expired items to add to the freelist.
This is generally not useful or required, unless you have memory
with very mixed TTLs, you do not fetch items frequently enough or
otherwise cause them to expire, and you don't want items with longer
TTLs block reclaiming expired items, or to be evicted early.
Future uses of the thread should allow examining and purging items
via a plugin interface: IE crawl all items matching some string
and remove them, or count them. It is simple to modify to experiment
with as of now.
See doc/protocol.txt for full explanation of related commands and