![(please configure the [header_logo] section in trac.ini)](/ThreadScope/chrome/site/your_project_logo.png){kind=logo}
Changes between Version 21 and Version 22 of RTSsummaryEvents
- Timestamp:
- 01/05/12 09:28:18 (17 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
RTSsummaryEvents
v21 v22 73 73 }}} 74 74 75 This computed in a quite convoluted way in the +RTS -s code. Ask JaffaCake if it could be simplified.75 This is computed in a quite convoluted way in the +RTS -s code. Ask JaffaCake if it could be simplified. 76 76 The current computation seems to be the following: total words copied during parallel GCs divided 77 77 by the average over all parallel GCs of maximal number of words copied … … 90 90 Ask JaffaCake how the "tasks" relate to the "threads" for which we generate 91 91 events. For now, to the existing GC events we can add the info about which task 92 does the job, but may miss something this way. BTW, is the time between event GCIdle and GCWork counted93 as GC time of the task?Generally, is GCIdle useful for us here in any way?94 Similarly, can be calculate the MUT (elapsed) times just but taking the total92 does the job, but we may miss something this way. BTW, ask JaffaCake if the time between event GCIdle and GCWork is included 93 in the GC time of the task or not. Generally, is GCIdle useful for us here in any way? 94 Similarly, can we calculate the MUT (elapsed) times just but taking the total 95 95 time a thread (or cap?) is run and subtracting the GC time and any pauses (and are all 96 96 pauses visible through events we have already?). … … 100 100 }}} 101 101 102 Tell JaffaCake that the example and description for th at at102 Tell JaffaCake that the example and description for the SPARKS count at 103 103 {{{ 104 104 http://www.haskell.org/ghc/docs/latest/html/users_guide/runtime-control.html#rts-options-gc … … 107 107 events for that (we calculate this using the SparkCounters events, 108 108 but we could also use the precise per-spark events). 109 110 109 111 110 {{{ … … 117 116 }}} 118 117 119 (Note that there may be more positions here, e.g., forprofiling.)118 (Note that there may be more times listed above, e.g., the time overhead of profiling.) 120 119 We can sum up the GC time from GC events. We'd also like to have the MUT 121 120 figure, but it's not obvious if we can manage to get it from all the thread (task)
