ghc-events-analyze: Analyze and visualize event logs

[ bsd3, development, profiling, program, trace ] [ Propose Tags ]

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:

  1. While ThreadScope shows CPU activity across all your cores, ghc-events-analyze shows CPU activity across all your Haskell threads.

  2. 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.

Downloads

Maintainer's Corner

Package maintainers

For package maintainers and hackage trustees

Candidates

  • No Candidates
Versions [RSS] 0.2.0, 0.2.1, 0.2.2, 0.2.3, 0.2.4, 0.2.5, 0.2.6, 0.2.7, 0.2.8 (info)
Change log ChangeLog
Dependencies base (>=4.5 && <4.8), containers (>=0.5 && <0.6), diagrams-lib (>=1.0 && <1.1), diagrams-svg (>=1.0 && <1.1), filepath (>=1.3 && <1.4), ghc-events (>=0.4 && <0.5), lens (>=3.10 && <4.1), mtl (>=2.1 && <2.2), optparse-applicative (>=0.7 && <0.8), parsec (>=3.1 && <3.2), SVGFonts (>=1.4 && <1.5), template-haskell, th-lift (>=0.6 && <0.7), transformers (>=0.3 && <0.4) [details]
License BSD-3-Clause
Copyright 2013-2014 Well-Typed LLP
Author Edsko de Vries, Duncan Coutts, Mikolaj Konarski
Maintainer edsko@well-typed.com
Category Development, Profiling, Trace
Source repo head: git clone https://github.com/edsko/ghc-events-analyze
Uploaded by EdskoDeVries at 2014-02-12T16:09:28Z
Distributions
Reverse Dependencies 1 direct, 0 indirect [details]
Executables ghc-events-analyze
Downloads 5595 total (29 in the last 30 days)
Rating 2.0 (votes: 1) [estimated by Bayesian average]
Your Rating
  • λ
  • λ
  • λ
Status Docs not available [build log]
Successful builds reported [all 7 reports]