> For the complete documentation index, see [llms.txt](https://razortheory.gitbook.io/unicef-project-connect/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://razortheory.gitbook.io/unicef-project-connect/technical-documentation/performance-improvements.md).
# Performance
Despite data being aggregated, to achieve acceptable performance we use caching altogether with gzip compression. Compression is essential for heavy responses, for example country boundaries and school points.
Caching is used to store responses entirely and being updated by background worker to avoid API performance issues caused by re-generating expired responses.\
More information can be found in `SoftCacheManager` mixin. The main idea is to return cached data even in case of expiration and run background task to update info. It means, first request after expiration will trigger cache key update and receive old information instead of trying to update info synchronously. Also, cache is being updated periodically if not requested by user for a long time to keep cached information up to date.
---
# 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://razortheory.gitbook.io/unicef-project-connect/technical-documentation/performance-improvements.md?ask=&goal=
```
`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.