Repository navigation
Layer 1 microVM: density measured (N VMs, PSS, KSM, restores under load) - #89
Merged
Merged
Conversation
…ity) PSS and RSS of 1, 4, 8 and 16 VMs at 512 MiB and 256 MiB guests, KSM off and on, restores while the others run and one serves a load, and that VM's front-page p50. Restored VMs share nothing (each site restores its own snapshot), KSM merges nothing (guest memory isn't mergeable), and a foreign vm.mem is rebuilt, not shared. Written up in docs/layer1-microvm.md: keep 512 MiB and 5 workers; a snapshot sites share is follow-up 13.
…y-72 # Conflicts: # docs/layer1-microvm.md # test/ext-microvm.sh
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.
Part 5 of #72: density, measured. This is measurement only; no product default changes. Stacked on #88 (it uses that PR's
mvm_filesintest/ext-microvm.sh), so review that one first. closes #72What changed
test/ext-microvm.sh densityruns N sites' microVMs at once (DENSITY_NS, default1 4 8 16;DENSITY_MEM, default 512). Each site is a copy of the test site in its own volume and state folder, one VM per site, as the product runs them. For each N it records:docs/layer1-microvm.mdhas a new section, "Density: N sites on one host", with the tables and the recommendation. Follow-up 11 now points to it, and follow-up 13 (a snapshot that sites share) is new.Results ([xps]: 4 cores, 7.5 GiB, other agents' stacks running; all three layers on, Contact Form 7 isolated)
512 MiB guests:
256 MiB guests: 245 MiB at N=1, 920 MiB at N=8 and 1397 MiB at N=16, with the same p50 (135.7–137.1 ms, 100/100 200s).
vm.mem.vm.memto site 1's. Each launcher rebuilt its own snapshot instead, taking 1.6–4.0 s to "ready".Recommendation: keep 512 MiB and php-fpm's 5 workers.
More density needs a snapshot that sites share (taken before the site disk is attached), or mergeable guest memory for KSM. Both are launcher changes (follow-up 13).
Evidence
test/ext-microvm.sh's checks (no mode): exit 0, 196 ok, 0 FAIL.-D warnings+cargo test): exit 0. No Rust changed.There is no revert proof: this PR adds a measurement mode and no check.
-claude