kevin@kosman.UUCP (Kevin O'Gorman) (06/25/90)
I was running through the examples in my new Turbo Profiler, and one of them ran very differently from what the manual said I should expect. They replaced printf calls with cprintf calls because they are "faster" than printf. However, the screen scrolling under cprintf is so painfully slow that I can watch it 'wash' its way down the screen. The running time of the routine, instead of dropping somewhat, went up by a factor > 10! Does anyone have an idea what the problem is, or where I should look? The obvious suspects seem to be these: 1 The profiler (unlikely) 2 The cprintf code itself 3 The console driver (I use ANSI.SYS) 4 The CGA adapter 5 The fact that I'm not running monochrome. The next sample removed most of the linefeeds, and indeed ran pretty fast so long as I arranged for the screen to start out mostly blank so that there was no scrolling. Thanks. -- Kevin O'Gorman ( kevin@kosman.UUCP, kevin%kosman.uucp@nrc.com ) voice: 805-984-8042 Vital Computer Systems, 5115 Beachcomber, Oxnard, CA 93035 Non-Disclaimer: my boss is me, and he stands behind everything I say.