ghc-events-analyze is a simple Haskell profiling tool that uses GHC's eventlog system. It helps with some profiling use cases that are not covered by the existing GHC profiling modes or tools. It has two major features:
While ThreadScope shows CPU activity across all your cores, ghc-events-analyze shows CPU activity across all your Haskell threads.
It lets you label periods of time during program execution (by instrumenting your code with special trace calls) and then lets you visualize those time periods or get statistics on them.
It is very useful for profiling code when ghc's normal profiling mode is not available, or when using profiling mode would perturb the code too much. It is also useful when you want time-profiling information with a breakdown over time rather than totals for the whole run.
The blog post Performance profiling with ghc-events-analyze describes the motivation in more detail.
* Add suppor for filtering threads by name, and improve
performance of relabelling.
(2017-03-11 Pepe Iborra <firstname.lastname@example.org>)
* Fix bug in timeline rendering when using --tick-every
(2016-10-04 Edsko de Vries <email@example.com>)
* Backwards compatibility with older ghc
* Add new command line options: `--tick-every`, `--bucket-width`,
`--bucket-height`, and `--border-width`. This allows to get both the
behaviour we used in the blogpost and the behaviour that was implemented
by Andrew Farmer in 0.2.1
(2016-10-03 Edsko de Vries <firstname.lastname@example.org>)
* Fix issue with thread creation before window start
(2015-09-29, Will Sewell <email@example.com>)
* Bump optparse-applicative and lens versions
(2015-01-19, Will Sewell <firstname.lastname@example.org>)
* Adds support for GHC 7.10
(2015-09-23, Will Sewell <email@example.com>)
(2015-05-29, GaneshRapolu <firstname.lastname@example.org>)
* Various new features: slice time more finely, add sorting options for timed
report, more colours, support for ms on the timeline, use alternating
colours for background, support for windowing.
(2014-12-06, Andrew Farmer <email@example.com>)
* Make sure _shutdown is always set, so that event logs from programs
that terminated abnormally can still be visualized
(2014-03-14, Bas van Dijk <firstname.lastname@example.org>)
* Relax bounds
(2014-05-28, Dominic Steinitz <email@example.com>)
(2014-11-05, Alexander Vershilov <firstname.lastname@example.org>)
(2014-11-07, Andrew Farmer <email@example.com>)
* Move to diagrams 1.2
(2014-06-25, Carter Tazio Schonwald <firstname.lastname@example.org>)
* Fix space leak in recordShutdown
(2014-08-15, John Lato <email@example.com>)
* Initial release
(2014-02-12, Edsko de Vries <firstname.lastname@example.org>)