Changes between Version 26 and Version 27 of RTSsummaryEvents

Show
Ignore:
Timestamp:
01/10/12 09:04:56 (18 months ago)
Author:
MikolajKonarski (IP: 95.160.111.162)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • RTSsummaryEvents

    v26 v27  
    6969between seq and par GC. We'd need to split the current GC events into generations, though, 
    7070to report for every generation separately. We may and up with two tables for the same GC info: 
    71 one aggregated by cap, another by generations. Note that we don't want  
    72 to report the CPU time, only the elapsed time, and that's fine. 
     71one aggregated by cap, another by generations. Or, as long as there are only 2 generations, 
     72one table with both caps and generations, with the following rows: cap0&gen0, cap0&gen1, cap1&gen0, etc.  
     73Note that we don't want to report the CPU time, only the elapsed time, and that's fine. 
    7374 
    7475{{{