When using SCCACHE_CLIENT_SIDE the stats report is not properly populated
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 7.7k
- Forks
- 748
- Avg merge
- 4d 7h
- Merged PRs (30d)
- 21
Description
When using SCCACHE_CLIENT_SIDE Cache hits 516 is reported correctly, but L0 (disk) hit rate and L1 (webdav) hit rate - is not.
For debugging it is useful to have these stats show correctly.
conanfile.py (...): RUN: sccache --stop-server
Stopping sccache server...
Compile requests 0
Compile requests executed 516
Cache hits 516
Cache hits (C/C++) 516
Cache misses 0
Cache hits rate 100.00 %
Cache hits rate (C/C++) 100.00 %
Cache timeouts 0
Cache read errors 0
Forced recaches 0
Cache write errors 0
Cache errors 0
Compilations 0
Compilation failures 0
Non-cacheable compilations 0
Non-cacheable calls 0
Non-compilation calls 0
Unsupported compiler calls 0
Average cache write 0.000 s
Average compiler 0.000 s
Average cache read hit 0.019 s
Failed distributed compilations 0
Multi-level cache levels 2
L0 (disk) hits 0
L0 (disk) misses 0
L0 (disk) hit rate -
L0 (disk) writes 0
L0 (disk) write failures 0
L0 (disk) backfills from 0
L0 (disk) backfills to 0
L0 (disk) avg cache write 0.000 s
L0 (disk) avg cache read hit 0.000 s
L1 (webdav) hits 0
L1 (webdav) misses 0
L1 (webdav) hit rate -
L1 (webdav) writes 0
L1 (webdav) write failures 0
L1 (webdav) backfills from 0
L1 (webdav) backfills to 0
L1 (webdav) avg cache write 0.000 s
L1 (webdav) avg cache read hit 0.000 s
Cache location Multi-level (2 levels)
L0 (disk) Local disk: "/home/user/.cache/sccache"
L1 (webdav) webdav, name: , prefix: /
Base directories /home/user/repos/src/, /home/user/.conan2/
Version (client) 0.17.1
Cache size 35 KiB
Max cache size 10 GiB
Best regards.
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
Reproduce the reported output with SCCACHE_CLIENT_SIDE and compare the aggregate cache-hit statistics with the per-level L0 and L1 values. Trace the stats-reporting path responsible for these lines and verify the result against the shown multi-level cache configuration. Done means the per-level hit and hit-rate fields reflect the actual cache activity instead of zeroes and dashes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100