Myasnikov Daniil
7291257f4b
TEMPORARY, investigation only, same throwaway branch, never merged. The arms already here price INDEPENDENT work: 24 threads on 16 cores, each running its own loop. Guest vCPUs are not independent. SMP bring-up, IPIs and lock handoffs all need several vCPUs on a core at the same instant, and no throughput figure can see that -- which is why the aggregate numbers from the scaling arms cannot answer the question the e2e pinning change rests on. That question is whether two vCPUs of ONE guest sharing a physical core costs more than two vCPUs of DIFFERENT guests sharing one. The runner's scheduler cannot draw the distinction, because nothing above it says which threads are coupled, so if the distinction is real it is ours to express and if it is not there is nothing to express. Three groups of eight processes, all running at once, each round a fixed chunk of work then a barrier: a round ends only when all eight arrive, so a process off-core holds up the seven on it. Three placements. `same` and `cross` are held to the SAME twelve cores with the SAME doubling and differ only in whether the pair sharing a core belongs to one group -- without that matching the comparison measures core count, since a placement over sixteen cores beats one over twelve whatever the pairing. `float` sets no affinity and is the reference point rather than part of the controlled comparison. The statistic is the median of per-repeat same/cross ratios, not a ratio of aggregates: arms are interleaved so drift lands in all three equally, and pairing two measurements taken seconds apart removes most of what is left. The verdict is written before the run -- every repeat above 5% means the distinction is real, every repeat inside 5% means it is not and the e2e change is not worth a run, anything else concludes nothing. A barrier blocks rather than spins, so a waiting process leaves its sibling the whole core. That is the co-scheduling half of the claim and not the spin-wait half, where a preempted lock holder also burns its sibling's cycles, so this reads as a lower bound on the effect. Assisted-By: Claude <noreply@anthropic.com> Signed-off-by: Myasnikov Daniil <myasnikovdaniil2001@gmail.com>
Cozystack
Cozystack is a free platform and framework for building clouds.
Cozystack is a CNCF Sandbox Level Project that was originally built and sponsored by Ænix.
With Cozystack, you can transform a bunch of servers into an intelligent system with a simple REST API for spawning Kubernetes clusters, Database-as-a-Service, virtual machines, load balancers, HTTP caching services, and other services with ease.
Use Cozystack to build your own cloud or provide a cost-effective development environment.
Use-Cases
-
Using Cozystack to build a public cloud
You can use Cozystack as a backend for a public cloud -
Using Cozystack to build a private cloud
You can use Cozystack as a platform to build a private cloud powered by Infrastructure-as-Code approach -
Using Cozystack as a Kubernetes distribution
You can use Cozystack as a Kubernetes distribution for Bare Metal
Documentation
The documentation is located on the cozystack.io website.
Read the Getting Started section for a quick start.
If you encounter any difficulties, start with the troubleshooting guide and work your way through the process that we've outlined.
Versioning
Versioning adheres to the Semantic Versioning principles.
A full list of the available releases is available in the GitHub repository's Release section.
Contributions
Contributions are highly appreciated and very welcomed!
In case of bugs, please check if the issue has already been opened by checking the GitHub Issues section. If it isn't, you can open a new one. A detailed report will help us replicate it, assess it, and work on a fix.
You can express your intention to on the fix on your own. Commits are used to generate the changelog, and their author will be referenced in it.
If you have a concrete feature request, open an issue. For a cross-cutting or architectural change, open a design proposal in the community repo. For questions or early ideas, use GitHub Discussions. See CONTRIBUTING.md for the full routing.
Community
You are welcome to join our Telegram group and come to our weekly community meetings. Add them to your Google Calendar or iCal for convenience.
License
Cozystack is licensed under Apache 2.0.
The code is provided as-is with no warranties.
Commercial Support
A list of companies providing commercial support for this project can be found on official site.