[GHC] #8733: I/O manager causes unnecessary syscalls in send/recv loops

[GHC]

#8733: I/O manager causes unnecessary syscalls in send/recv loops
-------------------------------------+------------------------------------
        Reporter:  tibbe             |            Owner:  simonmar
            Type:  bug               |           Status:  new
        Priority:  normal            |        Milestone:
       Component:  Runtime System    |          Version:  7.6.3
      Resolution:                    |         Keywords:
Operating System:  Unknown/Multiple  |     Architecture:  Unknown/Multiple
 Type of failure:  None/Unknown      |       Difficulty:  Unknown
       Test Case:                    |       Blocked By:
        Blocking:                    |  Related Tickets:
-------------------------------------+------------------------------------

Comment (by etrepum):

 Is the IO manager the right layer to be approaching this from? Not all
 protocols are going to be strictly request/response with no pipelining or
 multiplexing like vanilla HTTP is.

 Why not implement this at a higher level in a library that encapsulates
 these best practices for various sorts of protocols?

 A good start may be to add this to the Performance Resource:
 http://www.haskell.org/haskellwiki/Performance (which looks old but that's
 what came up when I searched). Erlang publishes an Efficiency Guide that
 is nice (but doesn't cover any networking topics)
 http://erlang.org/doc/efficiency_guide/users_guide.html

--
Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/8733#comment:5>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler