Subject: Re: commit -- Working STL vector support
From: Martin Sevior (msevior@mccubbin.ph.unimelb.edu.au)
Date: Mon Dec 18 2000 - 21:26:58 CST
This appears to be great stuff. Keeping UT_Vector classes really helps our
portability plus I love the asserts inside the UT_Vector class. They've
helped me find many a nasty bug.
However as Thomas says lets not lose site of the fact that these
functions are being called way more often than neccessary.
Cheers
Martin
On Mon, 18 Dec 2000, Thomas Fletcher wrote:
<snip>
>
> Initial test with original vector class:
> System runs @ 350847 cycles/sec
> Running 10 loops of 50000 iterations
> 1067721053 cycles 3043.27 ms
> 1065270144 cycles 3036.28 ms
> 1064068227 cycles 3032.86 ms
> 1062944582 cycles 3029.65 ms
> 1062888058 cycles 3029.49 ms
> 1062475271 cycles 3028.32 ms
> 1063600104 cycles 3031.52 ms
> 1064628594 cycles 3034.45 ms
> 1063410321 cycles 3030.98 ms
> 1063126250 cycles 3030.17 ms
>
<snip>
>
> Optimized version with prediction of 50000 elements:
> System runs @ 350847 cycles/sec
> Running 10 loops of 50000 iterations
> 5954521 cycles 16.97 ms
> 5027151 cycles 14.33 ms
> 4173265 cycles 11.89 ms
> 5411753 cycles 15.42 ms
> 5249518 cycles 14.96 ms
> 4523883 cycles 12.89 ms
> 4633118 cycles 13.21 ms
> 4662774 cycles 13.29 ms
> 4593791 cycles 13.09 ms
> 4240069 cycles 12.09 ms
>
This archive was generated by hypermail 2b25 : Mon Dec 18 2000 - 21:27:20 CST