X-Git-Url: http://git.megacz.com/?a=blobdiff_plain;f=docs%2Fusers_guide%2Fruntime_control.xml;h=2b16234496a254dbcba699bb000f4c7cc50e0b42;hb=f04dead93a15af1cb818172f207b8a81d2c81298;hp=d8735e209df1f6ddd83d03d5ae93421756bb6a6e;hpb=00fe691ba258b2d9c8d5d85a3dffc0224b426dd8;p=ghc-hetmet.git diff --git a/docs/users_guide/runtime_control.xml b/docs/users_guide/runtime_control.xml index d8735e2..2b16234 100644 --- a/docs/users_guide/runtime_control.xml +++ b/docs/users_guide/runtime_control.xml @@ -182,7 +182,7 @@ allocation area, size - [Default: 256k] Set the allocation area size + [Default: 512k] Set the allocation area size used by the garbage collector. The allocation area (actually generation 0 step 0) is fixed and is never resized (unless you use , below). @@ -298,51 +298,58 @@ - - RTS + + RTS option - [New in GHC 6.12.1] Disable the parallel GC. - The parallel GC is turned on automatically when parallel - execution is enabled with the option; - this option is available to turn it off if - necessary. + [New in GHC 6.12.1] [Default: 0] + Use parallel GC in + generation gen and higher. + Omitting gen turns off the + parallel GC completely, reverting to sequential GC. - Experiments have shown that parallel GC usually - results in a performance improvement given 3 cores or - more; with 2 cores it may or may not be beneficial, - depending on the workload. Bigger heaps work better with - parallel GC, so set your value high (3 - or more times the maximum residency). Look at the timing - stats with to see whether you're - getting any benefit from parallel GC or not. If you find - parallel GC is significantly slower - (in elapsed time) than sequential GC, please report it as - a bug. - - In GHC 6.10.1 it was possible to use a different - number of threads for GC than for execution, because the GC - used its own pool of threads. Now, the GC uses the same - threads as the mutator (for executing the program). + The default parallel GC settings are usually suitable + for parallel programs (i.e. those + using par, Strategies, or with multiple + threads). However, it is sometimes beneficial to enable + the parallel GC for a single-threaded sequential program + too, especially if the program has a large amount of heap + data and GC is a significant fraction of runtime. To use + the parallel GC in a sequential program, enable the + parallel runtime with a suitable -N + option, and additionally it might be beneficial to + restrict parallel GC to the old generation + with -qg1. - - RTS + + RTS option - [Default: 1] [New in GHC 6.12.1] - Enable the parallel GC only in - generation n and greater. - Parallel GC is often not worthwhile for collections in - generation 0 (the young generation), so it is enabled by - default only for collections in generation 1 (and higher, - if applicable). + [New in GHC 6.12.1] [Default: 1] Use + load-balancing in the parallel GC in + generation gen and higher. + Omitting gen disables + load-balancing entirely. + + + Load-balancing shares out the work of GC between the + available cores. This is a good idea when the heap is + large and we need to parallelise the GC work, however it + is also pessimal for the short young-generation + collections in a parallel program, because it can harm + locality by moving data from the cache of the CPU where is + it being used to the cache of another CPU. Hence the + default is to do load-balancing only in the + old-generation. In fact, for a parallel program it is + sometimes beneficial to disable load-balancing entirely + with -qb. @@ -529,21 +536,25 @@ - The total bytes allocated by the program. This may be less - than the peak memory use, as some may be freed. + The total number of bytes allocated by the program over the + whole run. - The total number of garbage collections that occurred. + The total number of garbage collections performed. - The average and maximum space used by your program. - This is only checked during major garbage collections, so it - is only an approximation; the number of samples tells you how - many times it is checked. + The average and maximum "residency", which is the amount of + live data in bytes. The runtime can only determine the + amount of live data during a major GC, which is why the + number of samples corresponds to the number of major GCs + (and is usually relatively small). To get a better picture + of the heap profile of your program, use + the RTS option + (). @@ -618,14 +629,14 @@ The "bytes allocated in the heap" is the total bytes allocated - by the program. This may be less than the peak memory use, as - some may be freed. + by the program over the whole run. - GHC uses a copying garbage collector. "bytes copied during GC" - tells you how many bytes it had to copy during garbage collection. + GHC uses a copying garbage collector by default. "bytes copied + during GC" tells you how many bytes it had to copy during + garbage collection. @@ -639,7 +650,10 @@ The "bytes maximum slop" tells you the most space that is ever - wasted due to the way GHC packs data into so-called "megablocks". + wasted due to the way GHC allocates memory in blocks. Slop is + memory at the end of a block that was wasted. There's no way + to control this; we just like to see how much memory is being + lost this way. @@ -652,7 +666,7 @@ Next there is information about the garbage collections done. For each generation it says how many garbage collections were - done, how many of those collections used multiple threads, + done, how many of those collections were done in parallel, the total CPU time used for garbage collecting that generation, and the total wall clock time elapsed while garbage collecting that generation. @@ -671,8 +685,8 @@ - Next there is the CPU time and wall clock time elapsedm broken - down by what the runtiem system was doing at the time. + Next there is the CPU time and wall clock time elapsed broken + down by what the runtime system was doing at the time. INIT is the runtime system initialisation. MUT is the mutator time, i.e. the time spent actually running your code. @@ -803,6 +817,92 @@ + + Tracing + + tracing + events + eventlog files + + + When the program is linked with the + option (), runtime events can + be logged in two ways: + + + + + + In binary format to a file for later analysis by a + variety of tools. One such tool + is ThreadScopeThreadScope, + which interprets the event log to produce a visual parallel + execution profile of the program. + + + + + As text to standard output, for debugging purposes. + + + + + + + + + RTS option + + + + Log events in binary format to the + file program.eventlog, + where type indicates the type + of events to log. Currently there is only one type + supported: -ls, for scheduler events. + + + + The format of the log file is described by the header + EventLogFormat.h that comes with + GHC, and it can be parsed in Haskell using + the ghc-events + library. To dump the contents of + a .eventlog file as text, use the + tool show-ghc-events that comes with + the ghc-events + package. + + + + + + + + RTS option + + + + Log events as text to standard output, instead of to + the .eventlog file. + + + + + + + + The debugging + options also + generate events which are logged using the tracing framework. + By default those events are dumped as text to stdout + ( + implies ), but they may instead be stored in + the binary eventlog file by using the + option. + + + RTS options for hackers, debuggers, and over-interested souls @@ -839,14 +939,28 @@ - num + x -DRTS option - An RTS debugging flag; varying quantities of output - depending on which bits are set in - num. Only works if the RTS was - compiled with the option. + + An RTS debugging flag; only availble if the program was + linked with the option. Various + values of x are provided to + enable debug messages and additional runtime sanity checks + in different subsystems in the RTS, for + example +RTS -Ds -RTS enables debug + messages from the scheduler. + Use +RTS -? to find out which + debug flags are supported. + + + + Debug messages will be sent to the binary event log file + instead of stdout if the option is + added. This might be useful for reducing the overhead of + debug tracing. + @@ -1020,12 +1134,22 @@ char *ghc_rts_opts = "-H128m -K1m"; itself. To do this, use the flag, e.g. $ ./a.out +RTS --info - [("GHC RTS", "Yes") + [("GHC RTS", "YES") ,("GHC version", "6.7") ,("RTS way", "rts_p") ,("Host platform", "x86_64-unknown-linux") + ,("Host architecture", "x86_64") + ,("Host OS", "linux") + ,("Host vendor", "unknown") ,("Build platform", "x86_64-unknown-linux") + ,("Build architecture", "x86_64") + ,("Build OS", "linux") + ,("Build vendor", "unknown") ,("Target platform", "x86_64-unknown-linux") + ,("Target architecture", "x86_64") + ,("Target OS", "linux") + ,("Target vendor", "unknown") + ,("Word size", "64") ,("Compiler unregisterised", "NO") ,("Tables next to code", "YES") ] @@ -1039,8 +1163,8 @@ $ ./a.out +RTS --info GHC RTS - Is this program linked against the GHC RTS? (Currently - the answer is always yes.) + Is this program linked against the GHC RTS? (always + "YES"). @@ -1054,45 +1178,71 @@ $ ./a.out +RTS --info RTS way - The variant (“way”) of the runtime. Possible - values are rts (vanilla), + The variant (“way”) of the runtime. The + most common values are rts (vanilla), rts_thr (threaded runtime, i.e. linked using the -threaded option) and rts_p (profiling runtime, i.e. linked using the -prof - option). Other variants include t - (ticky-ticky profiling) and dyn (the RTS is + option). Other variants include debug + (linked using -debug), + t (ticky-ticky profiling) and + dyn (the RTS is linked in dynamically, i.e. a shared library, rather than statically - linked into the executable itself). + linked into the executable itself). These can be combined, + e.g. you might have rts_thr_debug_p. - Target platform + + Target platform, + Target architecture, + Target OS, + Target vendor + - This is the platform the program is compiled to run on. + These are the platform the program is compiled to run on. - Build platform + + Build platform, + Build architecture, + Build OS, + Build vendor + - This is the platform where the program was compiled - from. (That is, the target platform of GHC itself.) Ordinarily + These are the platform where the program was built + on. (That is, the target platform of GHC itself.) Ordinarily this is identical to the target platform. (It could potentially be different if cross-compiling.) - Host platform + + Host platform, + Host architecture + Host OS + Host vendor + - This is the platform where GHC itself was compiled. + These are the platform where GHC itself was compiled. Again, this would normally be identical to the build and target platforms. + Word size + + Either "32" or "64", + reflecting the word size of the target platform. + + + + Compiler unregistered Was this program compiled with an “unregistered”