djackson 22568 (6/12/2013)
Now that is intriguing, because I don't see humans being suited to that task, at least not very efficiently.
I solved a performance/stability issue once by searching source code for instances where we made calls to C++ memory allocation functions. It would be somewhat trivial to produce a tool to handle this, or reconfigure the compiler to look for times when we allocated but did not delete.
Using a tool to do those things which we aren't very efficient at is a great use of resources.
Hi Dave, will not argue with you on your current train of thought but might add something. Not only should we control the memory leakages created by use leave and go on strategy but we should also have monitoring on the number of calls made to certain routines. Years back CICS use to track this in the IBM environs and we could see what was happening even on the system subroutine levels. With those in hand we could determine if the system was actually reusing the allocated mapped instance or was for some reason not sharing an instance but was always creating a new one. This left us at time with memory blocks all over the place and a massive cleanup effort going on regularly on the OS level. When we were able to identify those routines we determined if they were really necessary or if we were abusing a routine unnecessarily or ff it was just popular. If it was popular we could load it up early in the CICS region and make it stay resident, and almost force programs to use the one instance. Saved a lot of execution time.
M....
Not all gray hairs are Dinosaurs!