We keep our sessions in mysql, and have found standard data isn't an
issue (expiry/other static fields), but we take a real hit loading our
serialized data (with storable). Recently we've updated the session
with a sort of lazy-loading method, with only loads that data if asked
for, and it's been a big plus. I would avoid storing anything not
needed in the session, since once you start to scale across servers, the hit
starts to get worse and worse, as you need a central repository for
sessions, which isn't easily replicated.
Matt Grommes wrote:
I used some code from somebody else on the list that stores the
session on the filesystem. I hadn't gone beyond just that code so if
the db is faster, I'll be sure to use that and pull the rest of the
data from the db as well if the session isn't good for that. Thanks.
Perrin Harkins wrote:
On Thu, 2005-12-22 at 11:00 -0700, Matt Grommes wrote:
I'm new to using MasonX::Request::WithApacheSession for sessions so
I'm wondering what people's experiences are with how much data you
can put into that session without bogging things down?
Very, very little. Using your session as a cache is not a good plan.
I'd like to put a potentially large (100-200+) array of numbers in a
session so I don't have to pull the data out of the database all
over the site
Isn't your session being stored in the database? That is the fastest
available storage for Apache::Session.
- Perrin
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Mason-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mason-users
