RE: [cinjug-users] How much data can session store?

[Amol Deshmukh <adeshmukh@xxxxxxxxxxxxxx>]

In addition, if you are in a clustered environment, objects in HTTPSession

may be serialized and synchronized with the secondary server everytime

you call setAttribute.

~ amol

-----Original Message-----
From: Tom Rose [mailto:tom.rose@xxxxxxxxxxxx]
Sent: Tuesday, November 01, 2005 11:05 PM
To: lei.han@xxxxxxxxxxxxx; users@xxxxxxxxxx
Subject: RE: [cinjug-users] How much data can session store?

Lei,

 

Not sure about a way to limit the session size in a particular container. However, best practice is to keep HTTPSession as small as possible for each user. If configured for persistent session, remember it will get serialized and stored, so from a query and store perspective the larger it gets the slower it will be to perform these operations. When you get into a clustered configuration, you may have in-memory session replication for fail over, or just persisted as noted before.

 

So to answer you question, you need to get familiar with what is being done with HTTPSession in your particular container configuration. Then if the HTTPSession behavior (persistent, replication, etc) is consistent with the behavior required for the cached data, there is no advantage to building another cache. If the data does not have the same requirements, then yes there may be advantage to creating another cache.  Regardless of what is chosen, you will still have to performance profile the application to see how its behaving, and ultimate tuning of the JVM is always a good idea.

 

Best Regards,

Tom

--
Tom Rose
CTO, i-Konect
210.568.0466
tom.rose@xxxxxxxxxxxx


Empowering people with information that Moves!

 

---

From: lei.han@xxxxxxxxxxxxx [mailto:lei.han@xxxxxxxxxxxxx]
Sent: Tuesday, November 01, 2005 9:55 PM
To: users@xxxxxxxxxx
Subject: [cinjug-users] How much data can session store?

How can I find out the size limit of session data for my container?

If I write a cache utitlity, theroetically it can hold data up to JVM limited size. How about session? If I store the data in session, what's the limit? And would it substantially affect performance than storing it in regular cache instead?

Thanks!

Lei Han