[development] sessions problem
gerhard at killesreiter.de
Wed Dec 24 04:47:12 UTC 2008
-----BEGIN PGP SIGNED MESSAGE-----
Larry Garfield schrieb:
> On Tuesday 23 December 2008 9:20:52 pm Moshe Weitzman wrote:
>>> If the phpFreeChat module has a lot of data in there, I'd look at
>>> the module to see what it's doing with $_SESSION. It may be
>>> storing data there it doesn't need to and/or not removing data
>>> later on when it doesn't need it anymore. It really depends on
>>> the modules you have installed. OG, for instance, stores the
>>> complete node of the current group a user is viewing in the
>>> session, which makes the session table get really big (far too
>>> big, IMO). Other modules don't store more than int or two in the
>>> session, if that.
>> OG used to do that, but has changed in D6 and about to be released
>> D5. We only do that for authenticated users now, and it gets
>> cleared out when user visits a non group page.
> Ah, good to hear. That's still going to be a few hundred meg for my
> site, though. :-) What's the logic for that? Just to avoid
> node_load time?
This is IMNSHO still a horrible design decision. Session data is
updated every page view and storing the node in there will increase
the traffic between Web front ends and mysql server (and the mysql
master and the mysql slaves, if you are set up like this) quite a bit.
If you need to keep the OG context, you should only store that context
and not all other node metadata in the session.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
-----END PGP SIGNATURE-----
More information about the development