Myasnikov Daniil
920ab73d10
TEMPORARY, investigation only, same throwaway branch, never merged. lscpu reports this class as 32 MiB of L3 in two instances, eight cores to a domain. That is what the hypervisor ADVERTISES. The sibling map was advertised too and the arms already here showed it to be real; nothing has ever tested the cache map, and every claim about a sandbox node straddling two L3 slices rests on it. Neither side of the stack answers it. OCI documents the OCPU-to-core relation and confines NUMA and BIOS tuning to bare metal, stating no CCD or NUMA alignment guarantee for VM shapes anywhere; the launcher in cncf/automation sets no PlatformConfig at all, so nothing asks for alignment and nothing reports what was granted. Whatever the placement engine did is what we got. The discriminator is capacity contention between two DISTINCT physical cores, so SMT is not in this at all -- that was the previous experiment. Each worker walks its own dependent chain over its own array, built after it pins so the pages are its own rather than a copy-on-write share, and the footprint is swept across the advertised domain size and half of it. Two cores sharing a domain must fit two footprints in one cache; two on different domains get a cache each. A real split separates the curves at half the working set; curves lying on top of each other mean the split is not something our guests pay for. The chain is `i = arr[i]` over a multiplicative permutation, which is a dependent load: the next address is unknown until the current one returns, so no prefetcher can run ahead, and the footprint is exactly four bytes per slot. Verified locally to resolve the hierarchy, 0.018s at 1 MiB against 0.056s at 32 MiB over the same step count, and to refuse rather than guess on a machine that advertises a single domain. 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.