[erlang-questions] Obsolete exported functions file:raw_{read, write}_file_info/2 - why?

Zabrane Mickael zabrane3@REDACTED
Thu Sep 15 12:33:34 CEST 2011

Thanks a lot.

On Sep 15, 2011, at 12:25 PM, Joseph Norton wrote:

> Zabrane -
> Based on benchmarking results, I believe prim_file:read_file is a better alternative for performance.   The other reason the prim_file approach is better is it should prevent callers with file i/o to different disks and/or different disk controllers from impacting each other.  We have seen a case in production where failure of one disk crashed erlang processes doing file i/o to an unrelated disk.  The root cause (not yet repeated and not yet proven though) is the singleton file i/o server process.
> Nevertheless, I was hoping to learn from my original post why the file module hasn't been written (or re-written) to provide raw support for other operations beyond just open.  My only guess is that file i/o hasn't been a bottleneck for most Erlang applications.
> thanks,
> Joseph Norton
> norton@REDACTED

More information about the erlang-questions mailing list