Skip to contentSkip to conversation

Drastic Slowdown of 'fseek()' Calls From 2.4 to 2.6 -- VMM Change?

DISCUSSION Robert Hancock 1 participant 1 message Feb 24, 2006 1 message not in the archive

lore
Share & tools
lore
#1 lore raw
In reply to a message not in the archive
Quoted 1 line · Marr

Clearly, the 2.4.31 results are speedy because the whole 4MB file has been cached.

I don't think this is clear at all. The entire file should always be cached, not doing this would be insane.

Quoted 1 line

What I cannot figure out is this: what has changed in 2.6.x kernels to cause the performance to degrade so drastically?!?

fseek() is a C library call, not a system call itself - there may be something that glibc is doing differently. Are you using the same glibc version with both kernels?

Just from this program it could be something else entirely that explains the difference in speed, like the random number generator..

Signature · 3 lines
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from [email protected]
Home Page: http://www.roberthancock.com/