From: "Tony Ingenoso" 

Of that 500M only a small fraction will be meaningful though, the bulk of
it just wastes HDD space and never gets loaded because people never run
it.. Several profiling runs on typical user scenarios will quickly locate
the areas of the system that need attention.

The work that needs to be done once the profile data is available is the
same as its always been.  You don't need to understand it all - you just
need to understand those parts that are active participants.  Even then,
you don't need to know what the code is doing you need to know how its
behaving (slightly different notions).

If a performance guy can go to a developer and say "your keystroke
handling module is allocating and freeing 100 pages on every keystroke,
what's up with this?"  That will be good enough.

Don't laugh, I've seen an editor (one of Borland's first OS/2 apps) under
the OS/2 kernel debugger that allocated and freed a 1 byte segment on every
keystroke.  Every keystroke was two expensive trips through kernel memory
management.  Programmers do some pretty dumb things...

"Geo"  wrote in message
news:427e0b0d$1{at}w3.nls.net...
> "Tony Ingenoso"  wrote in message
> news:427d9332{at}w3.nls.net...
>
> Ah but there comes a point where the whole of the program/system is more
> than any one man can understand. 8M then 500M now, 200mhz then, 3ghz now.

--- BBBS/NT v4.01 Flag-5