[Building Sakai] Java 6 seems to be a problem for us

[Aaron Zeckoski]

That sounds about right. I agree, all of this stuff depends on load,
configuration, usage, etc.

If you run a lot of the JSF tools in your installation and they are
heavily used then your sessions are probably quite large and the total
number you have floating along with the sizes is what you care about.
You won't be able to get that info without connecting a profiler
unfortunately. I have used yourkit and jprofiler with Sakai and both
work well.

If you want a general sense of things, you can see the number of
sessions Sakai knows about using the online tool in the administrator
workspace.

-AZ


On Wed, Oct 14, 2009 at 1:04 PM, Charles Hedrick <hedrick at rutgers.edu> wrote:
> My assumption has been that the size of old is mostly based on the total
> amount of state that the system has to keep around for all sessions that are
> currently alive. That's going to be dependent upon load. We have 4
> production front ends, each handling between 500 and 1000 sessions,
> depending upon how you count. (500 is active in the last 2 min; 1000 is
> number of threads; actually the number of sessions active is almost
> certainly a lot larger than that, but it's not a number we track).



-- 
Aaron Zeckoski (azeckoski (at) vt.edu)
Senior Research Engineer - CARET - University of Cambridge
https://twitter.com/azeckoski - http://www.linkedin.com/in/azeckoski
http://aaronz-sakai.blogspot.com/ - http://tinyurl.com/azprofile