Run Time Stats

I am a student at University of Texas and was wondering what run time performance stats a developer would be interested in a java framework?
Memory usage, garbage collection, or average concurrency?
Thanks,
James

memory usage

Originally Posted by JamesF

I am a student at University of Texas and was wondering what run time performance stats a developer would be interested in a java framework?
Memory usage, garbage collection, or average concurrency?
Thanks,
James

An engineer at Java stated there are probably only five or six people in the world who know how to call System.gc correctly. The headers for gc have a comment, all too telling, that provides insight as to why Sun Java Real-Time System will likely reduce the exposure of gc to application code.

We get lots of requests for Memory usage, not enough platforms are true concurrent to generate requests from coders for concurrency work. I suggest doing Memory usage today, plan and delve into Concurrent, after getting memory useage shippable.

We have super-quads aleady shipping, 80 core already running on the bench, most expansion of computer processor power will be from true concurrency. Java is uniquely positioned to take the front in this due to support for concurrency being exposed in the api.