***
### Bottleneck Analysis
#### Resource Utilization
**1. CPU**
* CPU was **not** the bottleneck (usage \~**800%** on a 16-core machine)
* Execution, Merkle computation, and other pipeline stages all completed within the block time (\~**200 ms**)
CPU utilization during load test
**2. Memory**
* Memory grew continuously during the block cache fill phase, eventually reaching the **16 GB** limit
Memory growth as block cache fills
**3. Persistence (I/O)**
* Persistence latency was noticeably higher than the block time (\~**300 ms** vs \~**200 ms**)
* This caused the write buffer to accumulate and memory to grow
* Significant back-pressure appeared once the buffer reached the limit of **64**
Persistence latency vs. block time
---
# Agent Instructions: 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:
```
GET https://docs.gravity.xyz/developer-resources/benchmark-results.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.