Unfortunately Hubert doesn't who his times...sigh...
I expect that his major problem is between the first and second execution.
The first execution should always be slower that the second as it will
rearrange the cache for it's own use. This can be quite noticeable if
Hubert is running X with 16meg as it will have to start swapping in order to
accomodate 4Meg of data. 2nd and subsequent executions should show fairly
consistent behaviour as long as NOTHING else is done between them to change
the cache arrangement.
This does bring up an interesting point though...is there (or should there
be) a cache flush program? Would be real handy in situations like this.
Something which invalidates all cache pages would allow for consistent bench
marking.
-
/----------------------------------------------------------\
| Mike Black mblack@csihq.com 407-676-5118, x203 |
| Computer Science Innovations, Inc. 407-676-2355 FAX |
| Melbourne FL 32904-2314 http://www.csihq.com |
\----------------------------------------------------------/