70mb might not be much on a single server, but move to a clustered
environment and you might be in for some rude surprises...

Remember replication across the cluster... while 10k per session might not
be much, 5000-7000 sessions constantly replicating 10k across the cluster
could become an issue in the aggregate.

-- 
Frank W. Zammetti
Founder and Chief Software Architect
Omnytex Technologies
http://www.omnytex.com

On Thu, May 12, 2005 3:43 pm, Michael Jouravlev said:
> On 5/12/05, Leon Rosenberg <[EMAIL PROTECTED]> wrote:
>> Well the question was, why to use ActionForm if a POJO will do it es
>> well?
>
> Umm... No reason, unless one wants to use same ActionForm for input,
> edit, view, etc.
>
>> And keeping current object in session isn't a solution to all
>> problems...
>>
>> Just to give you an example, in our current application we have about
>> 5000-7000 active session
>> on each webserver. We have tons of object, so if we would keep
>> _EVERYTHING_
>> in session, what amount of ram the server would need?
>
> With 10K per session that would be 70 Megs. Not much. Also, I store
> only one object per session, this is why it is current. But I do not
> have to deal with 7000 sessions simultaneously :)
>
> On the other hand, you need to keep request data somewhere as well. It
> is the same RAM. Ok, request is cleaned automatically, session is not.
> To help with that, I have certain modes/pages, which invalidate
> session. Like, if I load item list, I invalidate current item. That
> is, I remove it from the session. I do not think that all users look
> at the item, and then leave the site. They might go to the list, and
> then leave the site ;) Also, session timeout can be adjusted.
>
> I am not saying here that my approach is the best. But I do not think
> that it is a "bad practice" either :)
>
> Michael.
>
> P.S. If a problem can be solved by adding more RAM, it is not a real
> problem ;) This is what Microsoft keeps proving with Windows: 640K,
> 1M, 4M, 16M, 64M... But people still use it, they just put more memory
> in their machines. Someone can still advertise OS which fits on one
> floppy and has full-blown GUI, multitasking, etc. But who cares, if
> polishing assembly code takes so much more than simply using VB?
>
> Don't want to start a flame. Just an opinion.
>
> ---------------------------------------------------------------------
> 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]

Reply via email to