Ability to disable tmp caching of phar contents
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 40.4k
- Forks
- 8.1k
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 96
Description
Description
It's not clear to me what the point of caching phar contents is. In a world where opcache is used, it shouldn't be necessary to cache the phar contents anyway, except perhaps the occasional data file.
In addition, since different threads / processes don't share phar caches, /tmp can get very crowded with lots of files caching near-identical data.
I maintain a long-running application in which autoload time is not a concern, but the hogging of tmp space is a problem for my users. There doesn't seem to be a way to stop ext-phar from caching things read from phars.
Contributor 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.
Research direction
Start by tracing ext-phar's phar-content caching and its /tmp usage, with opcache context in mind. Verify a way to disable that caching without affecting required phar reads; the issue names no files or tests, so locating the relevant entry points is part of the work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, php
- Domain
- backend, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100