> For the complete documentation index, see [llms.txt](https://docs.eclipse.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eclipse.xyz/architecture/eclipse-architecture/gsvm/gigacompute-design-principles.md). # GigaCompute Design Principles ## The Promises of the Layer 2 Roadmap Layer 1 blockchain typically rely on off-the-shelf hardware, leading to architectural constraints: * Serial execution models that limit concurrency * Inefficient memory access and cache patterns * Resource contention between unrelated applications. Layer 2 chains, on the other hand, are free to decouple performance from consensus. Furthermore, they are not limited by hardware constraints and can scale across multiple machines. While existing layer 2 chains have not yet gone beyond the scale of a single, powerful machine, GSVM promises to fully re-architect the execution stack. GSVM introduces the following concepts to the world of blockchain: **High-level** * Hardware/software co-design * Cross layer-optimizations * Strong isolation between applications, even under load supporting performance non-interference * Dynamic horizontal scaling **Network** * Near line-speed processing * Probabilistic (Bayesian) execution pre-confs * Performance-based sequencing * Latency-optimized tx routing **Runtime** * A self-improving runtime that relies on reinforcement learning * Computational abstraction * Hybrid concurrency to support transaction resource non-interference * Hotspot-aware hardware-affine scheduler guaranteeing isolation of applications under load **Database** * Disk-minimizing sequencer-driven caching * Hotspot-aware parallel NVMe array back-end supporting data non-interference * Hardware-accelerated SSD-aligned accounts DB * Fast state commitments for light clients --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.eclipse.xyz/architecture/eclipse-architecture/gsvm/gigacompute-design-principles.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.