From: simonmar Date: Mon, 16 May 2005 14:40:06 +0000 (+0000) Subject: [project @ 2005-05-16 14:40:06 by simonmar] X-Git-Tag: Initial_conversion_from_CVS_complete~541 X-Git-Url: http://git.megacz.com/?a=commitdiff_plain;h=df0ba686093aa147751b6aff6ecd73c91958f8c8;p=ghc-hetmet.git [project @ 2005-05-16 14:40:06 by simonmar] document +RTS -I --- diff --git a/ghc/docs/users_guide/runtime_control.xml b/ghc/docs/users_guide/runtime_control.xml index 837d99f..e779ce3 100644 --- a/ghc/docs/users_guide/runtime_control.xml +++ b/ghc/docs/users_guide/runtime_control.xml @@ -245,6 +245,39 @@ + seconds + + RTS option + + idle GC + + + + (default: 0.3) In the threaded and SMP versions of the RTS (see + , ), a + major GC is automatically performed if the runtime has been idle + (no Haskell computation has been running) for a period of time. + The amount of idle time which must pass before a GC is performed is + set by the seconds + option. Specifying disables the idle GC. + + For an interactive application, it is probably a good idea to + use the idle GC, because this will allow finalizers to run and + deadlocked threads to be detected in the idle time when no Haskell + computation is happening. Also, it will mean that a GC is less + likely to happen when the application is busy, and so + responsiveness may be improved. However, if the amount of live data in + the heap is particularly large, then the idle GC can cause a + significant delay, and too small an interval could adversely affect + interactive responsiveness. + + This is an experimental feature, please let us know if it + causes problems and/or could benefit from further tuning. + + + + + size RTS option stack, minimum size