> For the complete documentation index, see [llms.txt](https://polarischain-1.gitbook.io/polarischain/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://polarischain-1.gitbook.io/polarischain/7.-storage-and-persistence-architecture/7.5-performance-caching-and-memory-optimization.md).

# 7.5 - Performance Caching & Memory Optimization

With LMDB handling hot state via zero-copy reads, in-memory caching is strategically allocated to consensus-critical operations:

* **LRU Block Cache:** Recently accessed DAG blocks are cached with configurable memory limits, reducing disk I/O during wave certification.
* **DAG Traversal Memoization:** Leader-support and quorum-certification computations cache intermediate graph walks, eliminating redundant vertex scans during commit decisions.
* **HashSet Reference Lookups:** Round-linkage validation uses O(1) HashSet-based checks instead of linear scans, accelerating parent-reference verification across high-throughput rounds.

This layered storage architecture ensures Polarischain maintains sub-millisecond validation latency, deterministic consensus timing, and institutional-grade data durability—critical for payment SLAs, regulated asset settlement, and continuous network operation.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://polarischain-1.gitbook.io/polarischain/7.-storage-and-persistence-architecture/7.5-performance-caching-and-memory-optimization.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.