MetaCall level cache to avoid recompiling identical loader inputs
Maintainers usually reply within 1 day
Nobody has claimed this yet.
- #649 by @SATVIKsynopsis — closed without merging
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Begin with the rs_loader flow mentioned in the issue and trace when identical source inputs are compiled within one process. Establish whether a shared MetaCall core cache is feasible, define its cache key and compiled-artifact lifetime, and document a decided, testable design before implementation.
Written by the indexing model from the issue text.
Description
🚀 Feature
While inspecting rs_loader, it was noticed that the same source input can be compiled multiple times within a single MetaCall process under certain flows. This is not a bug, but a potential optimization opportunity.
Instead of introducing a loader specific cache, this could be handled at the MetaCall core level so that caching is shared across all loaders and languages thus, avoiding duplicated logic.
A possible approach could be a simple process local cache mapping source input to the compiled artifact, with no persistence. Opening this issue to discuss feasibility and design before any implementation.
- Dominant language
- C
- Stars
- 1.8k
- Forks
- 266
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 14
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
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.
More from metacall/core
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
metacall/core#964 · 1 comment ·
Maintainers usually reply within 1 day
-
pre-push hook empties VERSION when the clone has no tagsPossibly taken @vedant21-oss claimed this 18 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
metacall/core#939 · 3 comments ·
Maintainers usually reply within 1 day
-
TOCTOU race condition vulnerability!Possibly taken @akshatchitransh claimed this 1 day ago. Openbug
Difficulty 4/5 3-5 days Newbie friendliness 35/100
metacall/core#961 · 2 comments ·
Maintainers usually reply within 1 day
-
bug
Difficulty 3/5 Half a day Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Go Port Race Conditions on MacOSPossibly taken A pull request linked to this issue is open or already merged. Openbug
Difficulty 4/5 3-5 days Newbie friendliness 35/100
metacall/core#942 · 3 comments ·
Maintainers usually reply within 1 day
Similar issues
-
`table_create()` crashes when an `hccalloc()` for the option table failsPossibly taken @marinelay claimed this today. Opentype: bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
bug severity: low
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
AlessandroSangiuliano/Uros#950 ·
-
ESP32
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
Difficulty 1/5 1-3 hours Newbie friendliness 82/100
HandBrake/HandBrake#8266 · 1 comment ·
Maintainers usually reply within 1 day