Thanks for your advices, well I hope I can handle this problem.
Starky > That's *WAY* too much data in session. You should always strive to keep > session as small as possible, I believe the recommendation generally is > <32K. If you ever had to move to (or are already in?) a distributed > environment, 1.3Mb in session would absolutely kill you. Even on a single > box, because of the session persistance management chores, it could easily > be a problem. > > I would suggest looking at your requirements and see if there is a more > transient way of meeting the needs. > > -- > Frank W. Zammetti > Founder and Chief Software Architect > Omnytex Technologies > http://www.omnytex.com > AIM: fzammetti > Yahoo: fzammetti > MSN: [EMAIL PROTECTED] > > On Tue, January 10, 2006 9:58 am, starki78 said: > > Hi we are developing an application with > > Struts and I've a Action that creates > > 35 Charts writes it to the Session and displays it > > in a JSP. It runs on Tomcat 4.1. > > Most of the time it is fast but sometimes it takes significantly > > more time. I've tested all the methods, the session-size can > > reach a maximum of 1.3 MB. Is this too much? > > Where could be the bottle-neck? Has someone an idea? > > > > > > Thanks a lot > > Starky > > > > > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
