🚀 go-pugleaf

I have a really large unix application and have been working to get it to
compile in the msdos world using Turbo C++ and vroom.

I have messed around with the overlay buffer size and other tuning stuff
and still end up with a very slow application.  It just grinds on the 
disk, interestingly enough if I put the whole thing in a ram drive it
still is just as slow.   Thus it isn't the speed of the disk, but the
overlay management itself.

Anyone know the best approach to the vroom overlay management in terms
of the number of overlays vs. overlay size.  Is it better to have
60 or 70 large overlays or hundreds of smaller ones.  What about the
size of the overlay buffer vs the size of the largest overlay.  Any
tuning tips would be welcome.

Thanks

-Kevin

wizard@greylady.uoregon.edu
kevins@ori.org
kevins@ori.bitnet

--
--------------------------------------------------------------------------
                            Kevin D Smolkowski. J.D.

Also available at a machine near you!
Kevins@ori.org Kevins@cie.uoregon.edu wizard@chemstor.uoregon.edu

         "A conclusion is the place where you got tired of thinking."
--------------------------------------------------------------------------