openinteract-dev

[Openinteract-dev] Lazy session writing ?

[<And...@Be...>]

Hey !

monitoring our oi dbs I found, that loading and saving sessions does =
take
quite some time ( we stuff quite a bit of data in there .. ). In
OpenInteract.pm the step finish_cookies_and_session is executed, before =
the
page is returned to the browser. So, thechnically you could improve =
response
time a bit, if you delay this step until after the page is already =
returned
to the client. You could even register this sub to be carried out in =
the
cleanup phase of apache and not within the content handler like right =
now.

Still, I am not really sure, if this would bite you from behind, so I
thought I`d ask all you wise guys ;-).

later,


Andreas Nolte
- Leitung IT -
____________________________________

MSN Marketing Service Nordwest GmbH
- Bertelsmann Services Group -

Olympiastra=DFe 1
26419 Schortens

Fon +49 (0) 44 21 / 76 -84002
Fax +49 (0) 44 21 / 76 - 84111

E-Mail:And...@be...
Internet:www.bertelsmann-services.de

Re: [Openinteract-dev] Lazy session writing ?

[Chris W. <ch...@cw...>]

* Andreas Nolte (And...@Be...) [020620 06:23]:
> monitoring our oi dbs I found, that loading and saving sessions does take
> quite some time ( we stuff quite a bit of data in there .. ). In
> OpenInteract.pm the step finish_cookies_and_session is executed, before the
> page is returned to the browser. So, thechnically you could improve response
> time a bit, if you delay this step until after the page is already returned
> to the client. You could even register this sub to be carried out in the
> cleanup phase of apache and not within the content handler like right now.

That is an excellent idea. I'll try to implement this early next week
and see what happens.

Chris

Re: [Openinteract-dev] Lazy session writing ?

[Perrin H. <pe...@el...>]

And...@Be... wrote:
> monitoring our oi dbs I found, that loading and saving sessions does take
> quite some time ( we stuff quite a bit of data in there .. ).

You should probably try to move most of that out of the session. 
Putting a lot of data in a serialized session structure tends to be 
slower and less reliable than using normalized tables because you have 
to read/write the whole thing every time.

One thing that can help is a write-through cache.  You set things up so 
that it reads from a local cache instead of the db, and every time you 
write you go to the cache and the db.  You have to be sure that people 
will always return to the same server though, for this to work.

 > So, thechnically you could improve response
> time a bit, if you delay this step until after the page is already returned
> to the client.

Potentially dangerous if the save failed for some reason and the user 
didn't find out until later, but probably not a big deal.  I'd say go 
for it.

- Perrin