Funny you should ask this.
We just had a bad experience of this on our live server where previous developers had coded each logged in user to store a DataTable (using .NET) object into a session. The DataTable object was a couple of hundred KiloBytes and the session life was set to 1 hour. The live website could of had 50 simulateous users, and most of them close the browser when finishing with the site - so you can image that if in an hour period over 500 peopel access the site, and one hell of large chunk of data sitting in memory. This was causing chaos with the website, and was causing the IIS service to restart itself on a very frequently basis during one day (this killed all current user sessions).
Be wary of what you store in sessions and of the duration for which they stay on the server. I know I probs had the worse case scenario, but still it can happen
-----Original Message-----
From: php@xxxxxxxx
To: php-windows@xxxxxxxxxxxxx
Sent: Wed, 4 Apr 2007 3.34PM
Subject: Re: Sessions?
Hey Gustav
It depends so much on how much data you store in the session variables, what kind of storage you run (database or files and so on) and how many users you have, so it's really hard to say.
In my experience, sessions have very little impact on the server how ever long you set them to live.
Mike
Gustav Wiberg wrote:
> Hi there!
>
> How much impact on the server have sessions based on the length of minutes (seconds) that I change to? I just wonder if someone out there has > Any experience of this or know a place on the web that describes this...?
>
> Best regards
> /Gustav Wiberg
>
>
-- PHP Windows Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
