Biggest Delphi bottleneck?


I think the replacement memory manager was a great idea, and I know someone
who has recompiled a very large D7 project into D2006 and noted a
"significant speed increase" but not timed it so I can't say how big
"significant" is.

I remember when writing FastStrings I decided to try to write a POS routine
that worked better for my specific purposes (multiple finds for faster
replacement). However, despite how many times it was called in a loop it
hardly gave me any increase in speed at all. This was because 99.9% of the
bottleneck in StringReplace was in the reallocation of the result string
each time it was changed. If you improve something that takes only 0.01% of
the total time, you can only speed up your app by a maximum of 0.01%

So it leads me to ask the following question. Any opinions as to the
current biggest bottleneck in Delphi?


Pete


.