Xref: utzoo alt.msdos.programmer:1958 comp.os.msdos.programmer:246
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!know!samsung!zaphod.mps.ohio-state.edu!maverick.ksu.ksu.edu!unmvax!nmt.edu!jrwsnsr
From: jrwsnsr@nmt.edu (Jonathan R. Watts)
Newsgroups: alt.msdos.programmer,comp.os.msdos.programmer
Subject: Re: Overlay Advice for MSC5.1
Message-ID: <1990Jul26.034009.26377@nmt.edu>
Date: 26 Jul 90 03:40:09 GMT
References: <14359@onyx.BBN.COM>
Distribution: alt
Organization: New Mexico Institute of Mining and Technology
Lines: 18

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)