Flag unoserver image as alpha, add CPU pinning guidance#116
Merged
Conversation
The stirling-unoserver image is currently only published as :alpha; flag that explicitly so users don't try to pull :latest. Also add a CPU allocation and pinning subsection because the existing "one core pinned per active conversion" wording was being misread as a pinning instruction. Document both the soft cap (cpus:) and hard pinning (cpuset:) options, with a steer toward the soft cap.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
- Compatibility note: latest stirling-unoserver image is always compatible with the latest Stirling PDF, so tracking :latest (or :alpha today) on both needs no coordination. - Shorten the CPU allocation section to lead with "Core allocation between instances should be handled automatically", and drop the preamble, NUMA/HT detail, and closing tip block. - Rename the section from "CPU allocation and pinning" to "CPU allocation" and update the link from Host resource requirements. - Strip em dashes throughout.
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
1 participant
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.
Summary
Follow-up to #115. Two changes to
docs/Configuration/LibreOffice-Parallel-Processing.md:stirling-unoserverimage is only published as:alphatoday — the previous tags table implied:latestand:1.0.0were already available. Adds a:::caution Alpha releaseadmonition, restructures the tags table to flag status (Available now / Coming soon), and notes that the compose examples on the page still use:latestfor forward-compatibility so readers should substitute:alphafor now.### CPU allocation and pinningsubsection under "The stirling-unoserver Image" that:cpus:/--cpus) as the recommended approach when you want a CPU budget without giving up scheduling elasticity.cpuset:/--cpuset-cpus/ systemdCPUAffinity) with the cases where it's actually warranted (NUMA, noisy neighbours, benchmarked problem) and the tradeoff (lost elasticity, idle pinned cores).cpuset:only after benchmarking shows the scheduler is the bottleneck.Test plan
caution,tip) and the anchor link from Host resource requirements → CPU allocation and pinning.