Why does TLC gzip default to 'off'?
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 3.1k
- Forks
- 264
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 16
Description
I found gzip option saves about 88% disk spaces of state files (all-number named files, and overall is about 80%). And the performance loss (states found in 10 minutes) is less than 0.6%. I just test it for about 12 minutes and I don't know the result of the long run.
The TLA+ Toolbox does not have a gzip check box, and I found the gzip option was set to on by default and changed to off after a certain point.
Why does it default to off? Is gzip a good option for performance?
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 with the TLC gzip option and the linked change in PR 268, then compare the documented defaults and the reported state-file size and performance observations. Done means establishing why gzip is disabled by default and recording the supported performance trade-off, including any limits of the short test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100