Repository navigation
Add the Performance Test task, mode=perftest (fos#55) - #198
Merged
Merged
Conversation
A slow deploy is limited by one of three stages: the network, the CPU (decompression) or the target disk. Users had to be walked through debug mode to find which. fog.perftest times each stage and names the slowest. - Disk: a direct (uncached) sequential read of the target disk. Read only; nothing is written. - Network: reads the largest stored image over NFS, mounted read-only. The server sends a non-imaging task the dev/ capture share, so the stored images are its parent. - CPU: decompresses a sample of that image with the deploy's own decompressor (zstdmt -dc or pigz -dc). - Rates are uncompressed MB/s and GB/min, the unit partclone shows; the network rate is scaled by the sample's compression ratio. - The result is posted to service/perftest.php before the task is completed, so the server can store it on the host. A failed post is shown, not fatal. The logic is in perftest-funcs.sh so tests/checks/perftest.sh can run it off-target (35 cases; verified red by removing the dev/ mapping and by widening the sample glob). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Oct 27, 2026
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
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.
Closes #55.
A slow deploy is limited by one of three stages: the network, the CPU (decompression) or the target disk.
fog.perftesttimes each stage on its own and names the slowest. It runs as a new advanced task type, Performance Test, withmode=perftest. The FOG server half is in a fogproject PR and must merge first.What it measures
dev/capture share, so FOS mounts its parent.zstdmt -dcorpigz -dc).Results are posted to
service/perftest.phpbefore the task completes, so the server stores them on the host record. A failed post is shown on screen, not fatal.Tests:
tests/checks/perftest.sh, 35 cases, run against realzstdmt/pigzoutput. I proved it can fail: removing thedev/mapping fails 2a/2b, and widening the sample glob fails 3a.tests/run-all.sh: 31 passed, 0 failed.🤖 Generated with Claude Code