#5991: regression: huge number of wakeups in xmonad
--------------------------------------+-------------------------------------
Reporter: dmwit | Owner:
Type: bug | Status: new
Priority: high | Milestone: 7.4.2
Component: Runtime System | Version: 7.4.2
Resolution: | Keywords:
Os: Linux | Architecture: x86_64 (amd64)
Failure: Runtime performance bug | Difficulty: Unknown
Testcase: | Blockedby:
Blocking: | Related:
--------------------------------------+-------------------------------------
Comment(by dmwit):
The xmonad code base itself does not call threadDelay. However, the
xmonad-contrib packages do include three calls in various places:
* The XMonad.Prompt hierarchy use threadDelay after a prompt
autocompletion to wait for windows to finish drawing themselves. It is not
called in a background loop as far as I can tell; I expect it to be called
about once per keypress.
* XMonad.Util.Timer provides a timer. Possibly some configs use this
module and create a timer which renews itself every time it fires;
however, I think this is pretty uncommon. Many other modules import this
one, and may have loops, I didn't check.
* XMonad.Util.Run provides a function to spawn a process, wait a bit, and
then terminate it. I very much don't expect this to be called in a
background loop.
So, perhaps the next question is: does this problem occur with a stock
xmonad config (i.e. nothing more than "import XMonad; main =
defaultConfig")? If so, then we can confidently say there are no
background loops calling threadDelay.
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/5991#comment:13>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler
_______________________________________________
Glasgow-haskell-bugs mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
