Changes between Version 19 and Version 20 of RTSsummaryEvents

Show
Ignore:
Timestamp:
01/05/12 08:46:16 (3 years ago)
Author:
MikolajKonarski (IP: 95.160.111.162)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • RTSsummaryEvents

    v19 v20  
    88Here is a [https://github.com/Mikolaj/ThreadScope/raw/working/SummaryPanelMockup.png screenshot] 
    99of what we can already do using the current set of events. It happens we can do as much for the whole runtime  
    10 as for the time intervals in this case. The first line of +RTS -s follows. 
     10as for the time intervals in this case.  
     11 
     12The first line of +RTS -s follows. 
    1113 
    1214{{{ 
     
    4648}}} 
    4749                   
    48 No idea. Ask JaffaCake what the following formula means: 
     50No idea what new events we need to calculate fragmentation. Ask JaffaCake what the following formula from the RTS -s code means: 
    4951 
    5052{{{ 
     
    6062}}} 
    6163 
    62 Ask JaffaCake if RequestParGC is enough to tell seq/par and why some StartGC 
    63 follow neither RequestParGC nor RequestSeqGC (on the same capability, at least). 
    64 Split the current GC events into generations and into seq/par 
     64Ask JaffaCake if RequestParGC is enough to distinguish between seq and par GC and why some StartGC 
     65follow neither RequestParGC nor RequestSeqGC (on the same capability, at least, assuming I tested it right). 
     66 
     67We'd need to split the current GC events into generations and into seq/par 
    6568(if RequestParGC is not enough to tell seq/par). Note that we don't want  
    6669to report the CPU time, only the elapsed time, and that's fine.