Poor read() performance, and I can't profile it
kirk at strauser.com
Thu Jun 5 21:18:32 UTC 2008
On Thursday 05 June 2008, Kris Kennaway wrote:
> Kirk Strauser wrote:
> ktrace(1) and check for the buffer size in use. It is probably too
It seems to be doing a lot of read()s with 4096-byte buffers. Is that what
you mean? It's also doing a lot of lseek()s to what is likely the current
position anyway (example: seek to 0x00, read 16 bytes, seek to 0x10, etc.).
Would that make a difference, or should that be a NOP?
More information about the freebsd-questions