[erlang-bugs] file_server processes very large numbers of messages slowly

[Alexandru Scvorţov]

Hi Scott,

Thanks a lot for the suggestion.  We needed a few more functions than
just read_file_info(), including a few from filelib (which used file
internally).  We ended up writing a few wrappers around the prim_file
functions.  We also had a bit of problem hitting the open files limit,
but we already had a system in place to manage that.

Thanks again,

Alex

On Thu, Sep 15, 2011 at 01:24:48PM -0500, Scott Lystig Fritchie wrote:
> Alexandru, I'm about to hop on a plane, so I don't have much time.  Yes,
> your analysis appears sound.  There has been discussion in the last week
> on the mailing list that is related to prim_file and the file_server_2
> (registered proc name) process.
> 
> The probable answer (at least for now) is to write your own interface to
> the prim_file:read_file_info() (name?) function so that you can take
> advantage of the "+A n" I/O worker Pthread pool ... assuming of course
> that your workload doesn't overwhelm them to the point where selective
> receive doesn't bite you again.
> 
> -Scott
> 
>