Re (3): [Oberon] Bug report: Character insert speed in Edit under 8.24 alpha NO

[muller at inf.ethz.ch]

pat at picoworks.com wrote:
> I'm using the Vesa 2.0 driver at 1280x1024x16.

This is a linear frame buffer driver, which means the whole display
memory is mapped into the address space and all the raster operations
are implemented in software.

> This is on a 500MHz K6 with 256MB DRAM.

Perhaps the problem is slow memory copying in the display driver.
Anyway, the profiling should show what is going on.

BTW For accurate profiling, you need a test that runs the relevant
code for some time (more than 10 seconds).

Both profilers (StatProf and Profiler) are sampling the current 
EIP at a rate of 1000Hz, so 10s will give you 10000 samples.

StatProf was the first proof-of-concept implementation, and 
just gives the counts in a raw form, which you can use with 
Compiler.Compile *\f to find the actual code where time is spent.
It works well to find inner loops where lots of time is spent.

Profiler scans the call stack to find the active procedures on 
the stack and displays the nested structure of procedure calls.
It is more coarse-grained, but gives a better overview of why 
certain procedures are called.  It is useful if the inner loop
consists of many smallish procedures (e.g. a compiler or protocol).

-- Pieter

--
Pieter Muller, Computer Systems Institute, ETH Zurich / MCT Lab, Zurich
Native Oberon OS: http://www.oberon.ethz.ch/native/