[imp] [horde] large session entries in horde_sessionhandler

[Jan Schneider]

Zitat von liam hoekenga <liamr at umich.edu>:

> On our production servers, as soon as I log in to Horde, my entry in
> the session table includes about 23k of text in session_data.
>
> On our development servers, the same action generates a much smaller
> session_data (it only contains an array for hordeMessageStacks).
>
> Same software, same hardware, only difference is the amount of load the
> machine sees.  Does horde cache more when it's heavily loaded?  Is

No.

> there a way
> to limit the amount of information it caches in the session?

Nothing beyond the configuration items that you already know.

> Michael suggests that IMP doesn't store body contents in the session,
> but we've seen otherwise.  Our sessions contain messages - although I 
> don't know
> if they're the last message read, or the message currently being 
> read, if these
> messages contain attachments, the session data can grow quite large.  I don't
> think it's reasonable to suggest that the way to fix that is to limit 
> the size
> of the messages our users receive.

What session *variable* contains these messages? This might help 
trapping down where it gets into the session data, if you are sure that 
message caching is turned off on your production server.

Jan.

-- 
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/