Parser memory usage metrics

Open
#3,756 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
compilers, performance

Research direction

Start by examining the existing --profile-rule-parsing behavior and the related issues #3672 and #3647. Define a useful parser memory indicator for rules or ambiguities and specify how it should be reported; done means the metric identifies memory-heavy parsing behavior in the EVM semantics case.

Written by the indexing model from the issue text.

Description

The EVM semantics sometimes fail with OutOfMemory errors.
It is often because parsing takes a very long time and memory on specific rules.
It would be nice to have some sort of metric about what the parser is doing. If it's trying many ambiguities at runtime, we should detect those rules and print some data in --profile-rule-parsing.
Maybe we can count how many objects are being created by the parser.
@dwightguth, what would be a good indicator of memory usage in the parser?
If we know which rules are using a lot of memory, then we can debug further, we can adjust the definition, we can add parentheses...

Related:

  • #3672,
  • #3647
Dominant language
Python
Stars
591
Forks
163
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from runtimeverification/k

All issues in runtimeverification/k

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.