From 2119bdb88e9056fdef8a9c73a916429fb09cbc2d Mon Sep 17 00:00:00 2001 From: simonmar Date: Thu, 23 Jan 2003 12:26:04 +0000 Subject: [PATCH] [project @ 2003-01-23 12:26:04 by simonmar] Document +RTS -xt --- ghc/docs/users_guide/profiling.sgml | 25 +++++++++++++++++++++++-- 1 file changed, 23 insertions(+), 2 deletions(-) diff --git a/ghc/docs/users_guide/profiling.sgml b/ghc/docs/users_guide/profiling.sgml index 85d4f8a..e79e638 100644 --- a/ghc/docs/users_guide/profiling.sgml +++ b/ghc/docs/users_guide/profiling.sgml @@ -681,7 +681,7 @@ x = nfib 25 currently support mixing the and options. - There's one more option which relates to heap + There are two more options which relate to heap profiling: @@ -689,7 +689,7 @@ x = nfib 25 : - Set the profiling (sampling) interval to + Set the profiling (sampling) interval to secs seconds (the default is 0.1 second). Fractions are allowed: for example will get 5 samples per second. @@ -697,6 +697,27 @@ x = nfib 25 sampled on a 1/50 second frequency. + + + + RTS option + + + Include the memory occupied by threads in a heap + profile. Each thread takes up a small area for its thread + state in addition to the space allocated for its stack + (stacks normally start small and then grow as + necessary). + + This includes the main thread, so using + is a good way to see how much stack + space the program is using. + + Memory occupied by threads and their stacks is + labelled as “TSO” when displaying the profile + by closure description or type description. + + -- 1.7.10.4