Hi folks,
>From time to time I run into programs that make intensive use of
>co-expressions
and I've always found that tuning the memory parameters and optimizing them is
a
bit of a hit and miss thing. Recently this has been with certain Rosettacode
tasks but I've had a few non-hobby programs from time to time that hit this.
It
strikes me that I can't be the only one that would like more information on
this.
The various memory keywords provide almost no useful information to aid in
this. Results for the static region are typically 0. There is no easy way to
find out how big the static area is and how much of it is in use. Occasionally
you start to see static area collections which I understand aren't real
collections. Ralph once described them as phantoms. Yet something must be
triggering them. I know co-expression blocks don't move but are marked for
reuse.
I'm poking through the sources and I've noticed a number of undocumented
environment variables and I'm looking for better information on some of the
documented ones. I haven't got to the coexpr source yet as I want to update to
SVN first as I expect it might have changed.
I'm also poking through the monitoring programs to see if anything exists that
will help. There are two or three that look like a good place to start.
If anyone can suggest anything else, I'd appreciate hearing from you.
David
------------------------------------------------------------------------------
Magic Quadrant for Content-Aware Data Loss Prevention
Research study explores the data loss prevention market. Includes in-depth
analysis on the changes within the DLP market, and the criteria used to
evaluate the strengths and weaknesses of these DLP solutions.
http://www.accelacomm.com/jaw/sfnl/114/51385063/
_______________________________________________
Unicon-group mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/unicon-group
