| | 92 | |
| | 93 | |
| | 94 | {{{ |
| | 95 | INIT time 0.00s ( 0.00s elapsed) |
| | 96 | MUT time 0.42s ( 0.41s elapsed) |
| | 97 | GC time 0.29s ( 0.13s elapsed) |
| | 98 | EXIT time 0.00s ( 0.00s elapsed) |
| | 99 | Total time 0.71s ( 0.55s elapsed) |
| | 100 | }}} |
| | 101 | |
| | 102 | (Note that there may be more positions here, e.g., for profiling.) |
| | 103 | We can sum up the times from GC events. For other stats, we'd need the MUT |
| | 104 | figure, but it's not obvious if we manage to get it from all the thread (task) |
| | 105 | events that we have and will add above. It's also not clear if adding events |
| | 106 | needed to get the other times is worth it. After all the other events |
| | 107 | are added, let's see if we can get any more of these summary times, |
| | 108 | perhaps by adding a minor event emitted just once. Note that the INIT time is |
| | 109 | necessary for the Productivity figure below (it does not count as "productive |
| | 110 | time" in +RTS -s).. |
| | 111 | |
| | 112 | {{{ |
| | 113 | %GC time 89.5% (75.3% elapsed) |
| | 114 | }}} |
| | 115 | |
| | 116 | Ask JaffaCake why this line is in the docs, but not in the output |
| | 117 | of +RTS -s I've got. |
| | 118 | |
| | 119 | {{{ |
| | 120 | Alloc rate 564,074,971 bytes per MUT second |
| | 121 | }}} |
| | 122 | |
| | 123 | The events added above should suffice, except that we use elapsed time, |
| | 124 | not CPU time. |
| | 125 | |
| | 126 | {{{ |
| | 127 | Productivity 59.0% of total user, 76.6% of total elapsed |
| | 128 | }}} |
| | 129 | |
| | 130 | The events added above should be enough. Again. we only do the elapsed case. |