Changes between Version 21 and Version 22 of RTSsummaryEvents

Show
Ignore:
Timestamp:
01/05/12 09:28:18 (2 years ago)
Author:
MikolajKonarski (IP: 95.160.111.162)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • RTSsummaryEvents

    v21 v22  
    7373}}} 
    7474   
    75 This computed in a quite convoluted way in the +RTS -s code. Ask JaffaCake if it could be simplified. 
     75This is computed in a quite convoluted way in the +RTS -s code. Ask JaffaCake if it could be simplified. 
    7676The current computation seems to be the following: total words copied during parallel GCs divided 
    7777by the average over all parallel GCs of maximal number of words copied 
     
    9090Ask JaffaCake how the "tasks" relate to the "threads" for which we generate  
    9191events. 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 counted 
    93 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 total 
     92does the job, but we may miss something this way. BTW, ask JaffaCake if the time between event GCIdle and GCWork is included 
     93in the GC time of the task or not. Generally, is GCIdle useful for us here in any way? 
     94Similarly, can we calculate the MUT (elapsed) times just but taking the total 
    9595time a thread (or cap?) is run and subtracting the GC time and any pauses (and are all 
    9696pauses visible through events we have already?). 
     
    100100}}} 
    101101 
    102 Tell JaffaCake that the example and description for that at  
     102Tell JaffaCake that the example and description for the SPARKS count at  
    103103{{{ 
    104104http://www.haskell.org/ghc/docs/latest/html/users_guide/runtime-control.html#rts-options-gc 
     
    107107events for that (we calculate this using the SparkCounters events,  
    108108but we could also use the precise per-spark events). 
    109  
    110109 
    111110{{{ 
     
    117116}}} 
    118117 
    119 (Note that there may be more positions here, e.g., for profiling.) 
     118(Note that there may be more times listed above, e.g., the time overhead of profiling.) 
    120119We can sum up the GC time from GC events. We'd also like to have the MUT 
    121120figure, but it's not obvious if we can manage to get it from all the thread (task)