Sounds a good explanation, Riyad. I will be loading the DisplayObject directly from the DB with a query, and thus it seems that you agree on going with the smaller object.
Thanks. -----Original Message----- From: Riyad Kalla [mailto:[EMAIL PROTECTED] Sent: Thursday, May 27, 2004 12:16 PM To: Struts Users Mailing List Subject: Re: Session size Larry, It depends on how you load the elements. If you are creating the smaller objects by first loading the full objects, then just save the time and use the full ones. If however you are loading the DisplayObjects directly via a Hibernate query of course that will be magnitudes smaller. Also you may consider what the average size of your 200 Strings are. If its around 24 characters each (maybe a name, or name of something) that's say roughly 30 (object overhead is probably more) x 200 = 6000 bytes (6k) and maybe as high as 8k for overhead (I'm pulling numbers out of air here, I don't know the VM details on this). Where as your 5-string object is going to be considerably smaller (30 x 5 = 150 bytes, ~0.15K). I'd say if you can load the DisplayObject directly from the DB with a query, definately do that, especially if your employement trees can get large (100s or 1000s). Best, Riyad On Thursday 27 May 2004 09:06 am, Zhang, Larry (L.) wrote: > I would be more interested to know if we change the big elements in the > list to much smaller ones in the list, does it reduce the session (my > second part of question) at all? --------------------------------------------------------------------- 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]
