hlison@bbn.com (Herb Lison) (07/26/90)
Does anyone know of any software tools which can assist in designing an optimal overlay strategy for MSC5.1? We have a rather complex application which takes up about 400K of memory with no overlays. Through a simple-minded approach we have reduced this to about 200K with about a dozen overlays. Problem is that the system thrashes heavily with this overlay. Is there something that would tell us what is being most commonly called, either at runtime, or by off-line analysis of the code? Thanks in advance, Herb Lison
jrwsnsr@nmt.edu (Jonathan R. Watts) (07/26/90)
From article <14359@onyx.BBN.COM>, by hlison@bbn.com (Herb Lison): > Does anyone know of any software tools which can assist in designing > an optimal overlay strategy for MSC5.1? We have a rather complex > application which takes up about 400K of memory with no overlays. > Through a simple-minded approach we have reduced this to about 200K > with about a dozen overlays. Problem is that the system thrashes > heavily with this overlay. Is there something that would tell us > what is being most commonly called, either at runtime, or by > off-line analysis of the code? Borland's new Turbo Profiler (part of Turbo Debugger and Tools) can profile overlay activity...at least it can with Turbo language programs. I assume it will still work with CodeView programs converted to the Turbo format...anyone know for sure? - Jonathan Watts jrwsnsr@jupiter.nmt.edu (Internet address)