>> Ivek Szczesniak wrote: >>> The stdio implementation in libc is among the slowest stdio >>> versions out there. If you want to archive better performance you >>> should use the stdio implementation in libast or use mmap(2). >> This is an interesting implementation suggestion, but is outside the >> scope of PSARC because it does not affect the interfaces >> being proposed. We did achieve quite a speedup over the old method. >> We'll take another look. > >Using libast might well incur extra PSARC oversight -- are the libast >interfaces public? Consolidation private? If they are *project >private* then you'll need to get a contract for them. Using mmap() >would be free of those issues, and is likely to be the fastest without >imposing any new interdependencies.
I would suggest that you first measure before using libast. Typical, actual I/O operations takes a lot of time and the "ineffective fread implementation" time waste wouldn't be measurable. Casper
