Repository navigation
Train space estimate from measured project.licht; evict train entries last - #29
Merged
Merged
Conversation
… last Issue #28: a 9M, SH 3 run with 9 snapshots was estimated at 104 GB (about 23 GB expected), more than the disk had free, so gc_cache evicted the previous job's finished train directory, project.licht and all its snapshots, and only the service's stdout said so. - space_estimate("train"): project.licht at one generation per snapshot plus the final (2 without snapshots), 131 B + 2.1 B per SH coefficient per splat per generation, the line through the two measurements (3M/SH 1: 156 B, 6M/SH 3: 231 B). The restore-point copy is charged only when restore points are on. 6M/SH 3/9 snapshots: 69.9 -> 21.1 GB (15.7 GB measured); 9M: 104 -> 31 GB. - gc_cache evicts train entries after every other stage's, LRU within each: they hold the only copy of a job's snapshots and resume point. - ensure_space(job_id=) records what it evicted with the job that needed the room: the stage log (under the command line), runs/job<id>/ evictions.json, the job API (`evictions`) and telemetry (`evictions`, docs/job-telemetry.md). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Sf6XcYDnVaUaV1YZGbQyho
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue #28: a 9M, SH 3 run with 9 snapshots was estimated at 104 GB (about
23 GB expected), more than the disk had free, so gc_cache evicted the
previous job's finished train directory, project.licht and all its
snapshots, and only the service's stdout said so.
plus the final (2 without snapshots), 131 B + 2.1 B per SH coefficient
per splat per generation, the line through the two measurements (3M/SH 1:
156 B, 6M/SH 3: 231 B). The restore-point copy is charged only when
restore points are on. 6M/SH 3/9 snapshots: 69.9 -> 21.1 GB (15.7 GB
measured); 9M: 104 -> 31 GB.
each: they hold the only copy of a job's snapshots and resume point.
the room: the stage log (under the command line), runs/job/
evictions.json, the job API (
evictions) and telemetry (evictions,docs/job-telemetry.md).
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com
Claude-Session: https://claude.ai/code/session_01Sf6XcYDnVaUaV1YZGbQyho