What I have devised, and after some load testing appears to be working
is a mixed-bag method of solving this.
In effect, sessions are stored in the DB. When a returning user comes
to hte site, the session data is read from the DB and pushed into the
memcache. The memcache key is also stored in a
On Jun 15, 1:22 pm, Joseph Engo wrote:
Have you tried a bucketing approach ? (Using multiple NFS partitions
and/or directories instead of a single giant directory).
Yes, we tried that, using an additional 2 levels of dir, and it helped
a little, as we can now actual perform 'ls' on the dire
On Jun 15, 1:22 pm, Joseph Engo wrote:
> Have you tried a bucketing approach ? (Using multiple NFS partitions
> and/or directories instead of a single giant directory).
>
Yes, we tried that, using an additional 2 levels of dir, and it helped
a little, as we can now actual perform 'ls' on the
Have you tried a bucketing approach ? (Using multiple NFS partitions
and/or directories instead of a single giant directory).
On Jun 15, 2009, at 10:00 AM, tbs wrote:
David,
Thank you for the well thought out reply to my post, I agree with a
lot of what you said. Our current session hand
David,
Thank you for the well thought out reply to my post, I agree with a
lot of what you said. Our current session handler is actually using
NFS over RAID on a NAS, however we are finding that due to our
particular requirements (retain session data indefinitely, unless the
session file becomes
I'm not following your argument. First off, sessions in general are not a
good candidate for caching. Caching is in my opinion best reserved for data
that is primarily static, or has a high read to write ratio. Memcache when
used to front mysql for example, is preventing the overhead and content
On Jun 10, 2:55 pm, Brian Moon wrote:
> > The memcached server will sit on the same box as the MySQL server.
> > Given that on any given machine MySQL will try and take as much memory
> > as it can, does the invocation of memcached, with a memory allocation
> > that exceeds the available memory
The memcached server will sit on the same box as the MySQL server.
Given that on any given machine MySQL will try and take as much memory
as it can, does the invocation of memcached, with a memory allocation
that exceeds the available memory, cause the OS (linux) to pull the
difference from the
Hi,
I would like to use memCache and MySQL to handle PHP sessions in a
live environment. Unlike most of the examples out there that employ
write-through caching, our sessions change greatly from page view to
page view, so write-through would not help and I will be using write-
back caching. I am
