code sample: http://dpaste.com/114571/

that code runs on every request to a certain page, which is being hit
frequently. there are only 10 unique keys, and each of them gets
requested several times within the 5-minute window of cache
expiration.

however, what seems to happen is that things are cached correctly for
the first few minutes of restarting apache, but after that point,
there are far more misses than there should be. there should be only 1
miss for each of the 10 keys in each 5-minute period, but instead it's
90% misses.

apache, mod_python, memcached, ubuntu. i'm really puzzled as to what
this could be.

here's my memcached.conf for good measure. the only non-default is
that i've increated the RAM to 128M.

thanks in advance for any help you can offer! --lawrence


# memcached default config file
# 2003 - Jay Bonci <jaybo...@debian.org>
# This configuration file is read by the start-memcached script
provided as
# part of the Debian GNU/Linux distribution.

# Run memcached as a daemon. This command is implied, and is not
needed for the
# daemon to run. See the README.Debian that comes with this package
for more
# information.
-d

# Log memcached's output to /var/log/memcached
logfile /var/log/memcached.log

# Be verbose
# -v

# Be even more verbose (print client commands as well)
# -vv

# Start with a cap of 64 megs of memory. It's reasonable, and the
daemon default
# Note that the daemon will grow to this size, but does not start out
holding this much
# memory
-m 128

# Default connection port is 11211
-p 11211

# Run the daemon as root. The start-memcached will default to running
as root if no
# -u command is present in this config file
-u nobody

# Specify which IP address to listen on. The default is to listen on
all IP addresses
# This parameter is one of the only security measures that memcached
has, so make sure
# it's listening on a firewalled interface.
-l 127.0.0.1

# Limit the number of simultaneous incoming connections. The daemon
default is 1024
# -c 1024

# Lock down all paged memory. Consult with the README and homepage
before you do this
# -k

# Return error when memory is exhausted (rather than removing items)
# -M

# Maximize core file limit
# -r

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to