summaryrefslogtreecommitdiff
path: root/rts/eventlog
diff options
context:
space:
mode:
authorDuncan Coutts <duncan@well-typed.com>2012-02-17 02:55:29 +0000
committerDuncan Coutts <duncan@well-typed.com>2012-04-04 19:10:44 +0100
commitcd930da1145a0d6094e5b5380034e80d002d5b9a (patch)
treecb432a1a9c811bccebf10da8a60eecc9bcaf3841 /rts/eventlog
parent8536f09c2f310a95297b339de6084f77cc4044c1 (diff)
downloadhaskell-cd930da1145a0d6094e5b5380034e80d002d5b9a.tar.gz
Change the presentation of parallel GC work balance in +RTS -s
Also rename internal variables to make the names match what they hold. The parallel GC work balance is calculated using the total amount of memory copied by all GC threads, and the maximum copied by any individual thread. You have serial GC when the max is the same as copied, and perfectly balanced GC when total/max == n_caps. Previously we presented this as the ratio total/max and told users that the serial value was 1 and the ideal value N, for N caps, e.g. Parallel GC work balance: 1.05 (4045071 / 3846774, ideal 2) The downside of this is that the user always has to keep in mind the number of cores being used. Our new presentation uses a normalised scale 0--1 as a percentage. The 0% means completely serial and 100% is perfect balance, e.g. Parallel GC work balance: 4.56% (serial 0%, perfect 100%)
Diffstat (limited to 'rts/eventlog')
0 files changed, 0 insertions, 0 deletions