runtimeverification / runtimeverification/haskell-backend
Extend log processing tools to quantify _phases_ of execution
Nobody has claimed this yet.
- Dominant language
- Haskell
- Stars
- 224
- Forks
- 43
- PR merge metrics
- No merged PRs in 30d
Description
For performance optimisations, it would be important to know how much time which component, or which phase of request processing (e.g., matching, equation-based simplification, constraint checking, smt-solver interaction, internalisation) consumes.
This information could be gathered from a (complete!) context log file with timestamps, by grouping the time difference for suitable "spans" of log entries into categories and accumulating their time over an entire log file (or per request).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by examining the context log format and its timestamped entries. Define suitable spans for matching, simplification, constraint checking, SMT-solver interaction, and internalisation, then determine how accumulated durations should be reported for a whole log and per request. Done means complete logs produce timing totals grouped by phase.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- backend, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100