[GHC] #13164: idle time full GCs (idle cpu usage)
GHC
ghc-devs at haskell.org
Thu Jan 26 16:13:27 UTC 2017
#13164: idle time full GCs (idle cpu usage)
-------------------------------------+-------------------------------------
Reporter: lspitzner | Owner:
Type: feature request | Status: new
Priority: normal | Milestone:
Component: Runtime System | Version: 8.0.1
Resolution: | Keywords: idle GC
Operating System: Unknown/Multiple | Architecture:
| Unknown/Multiple
Type of failure: None/Unknown | Test Case:
Blocked By: | Blocking:
Related Tickets: | Differential Rev(s):
Wiki Page: |
-------------------------------------+-------------------------------------
Comment (by lspitzner):
I just noticed that this means that you do not get deadlock detection if
you forkIO (forever (threadDelay 100000)). That's interesting.
You are right, I was focused on GC performance instead of deadlock
detection because the latter was not even mentioned when i chatted with
rwbarton. Maybe he can comment on this.
Even for deadlock detection it makes sense to delay things based on the
cost of the full GCs. (I'd rather have to wait 15secs to get the deadlock
detected when I manage to create deadlocks than constantly be wasting CPU
time - but if full GCs are cheap, I would not mind quicker detection.)
--
Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/13164#comment:4>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler
More information about the ghc-tickets
mailing list