KO
|
EN
gitlite — search
Search
#python
#llm
#python3
#mongodb
#reactjs
#machine-learning
#kotlin
#ai
#java
#android
#react
#rust
hs-speedscope
★ 39
Open GitHub ↗
No description available.
Download README (.md)
Explore Similar Repositories
TemporalEventAnnotator
:
A QT tool used to annotate temporal segments of a video with events which each have unique and customisable information.
reu
:
List: Research Experience for Undergrads
laravel-vue-translation
:
A package to have laravel translation in VueJS
artee.ai
:
AI Generated Tees
ultragen
:
Desktop/web programming language/template engine
// repository documentation
Was this content helpful?
★ 0
(0 ratings)
Select Rating:
★
★
★
★
★
Submit Feedback
Recent Feedback
×
Download README
Do you want to download the
README.md
file for
hs-speedscope
?
Download (.md)
# hs-speedscope `hs-speedscope` is a simple executable for converting an eventlog into a format suitable to load into [speedscope](https://www.speedscope.app/). WARNING: Only GHC 8.10 supports generating an eventlog with the correct events for this program to work. ## Usage 1. Create an eventlog which contains time profiling events by running your program with `program +RTS -p -l-au`. 2. Run `hs-speedscope` on the resulting eventlog `hs-speedscope program.eventlog`. 3. Load the resulting `program.eventlog.json` file into [speedscope](https://speedscope.app) to visualise the profile. ## Installation ```shell cabal update cabal install exe:hs-speedscope ``` This will install to cabal's per-user default location: `~/.cabal/bin/hs-speedscope`. ## Filtering an eventlog It is sometimes useful to isolate a specific part of the sample, for example, when I was profiling ghcide, I want to isolate a single hover request. The `--start` and `--end` options can be used to indicate which parts of the eventlog to keep. The filtering options look for messages inserted into the eventlog by [`traceMarker`](https://hackage.haskell.org/package/base-4.12.0.0/docs/Debug-Trace.html#v:traceMarker) events. * No events before the first marker which matches the prefix given by `--start` will be included in the result * No events after the first marker which matches the prefix given by `--end` will be included in the result. For example, the following invocation will filter the profile between the START and END markers. ```shell hs-speedscope File.eventlog --start START --end END ```