#8046: Make the timer management scale better across multicore
------------------------------------+-------------------------------------
Reporter: tibbe | Owner:
Type: bug | Status: new
Priority: normal | Milestone:
Component: Compiler | Version: 7.6.3
Keywords: | Operating System: Unknown/Multiple
Architecture: Unknown/Multiple | Type of failure: None/Unknown
Difficulty: Unknown | Test Case:
Blocked By: | Blocking:
Related Tickets: |
------------------------------------+-------------------------------------
A recent commit
{{{
commit e843e73690f828498f6e33bb89f47a50c3ab2ac9
Author: Ian Lynagh <[email protected]>
Date: Sat Jun 8 20:19:59 2013 +0100
IO manager: Edit the timeout queue directly, rather than using an edit
list
Fixes #7653.
}}}
undid an optimization to the management of timeouts (to fix a bug, which
is good). We should check how much this hurt performance, but it might be
better to rewrite the timeout management altogether. The current scheme
scales poorly to several cores. We should probably have one priority queue
per core and use an efficient mutable data structure.
--
Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/8046>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler
_______________________________________________
ghc-tickets mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/ghc-tickets
