Live query, summary, or cache for a hot aggregate?
For engineers choosing how to serve an expensive aggregate at a known read rate.
Works with
- Codex
- Cursor
- GitHub Copilot
The prompt259 words · 3 blanks
What you fill in
- Query and plan evidence
[query_and_plan]ExampleAggregate SQL, EXPLAIN ANALYZE output, row counts, write rate, and current p95 latency - Peak reads per second
[peak_reads]Example800 - Freshness requirement
[freshness_need]ExampleUp to 5 seconds stale
How to use it
- 1Open it in PromptVault. Find it in Coding, or search for “Live query, summary, or cache for a hot aggregate?”.
- 2Fill in the 3 blanks. query and plan evidence, peak reads per second and freshness requirement — the only things the prompt cannot know.
- 3Copy and paste it into Cursor. It also works with Codex and GitHub Copilot.
About this prompt
“Live query, summary, or cache for a hot aggregate?” is a advanced coding prompt. For engineers choosing how to serve an expensive aggregate at a known read rate. It is 259 words long and written to get a usable answer on the first message, in Codex, Cursor and GitHub Copilot or any other chat assistant. Good for: decision making, sql, performance, comparison, architecture and deep dive. Like every prompt in PromptVault, it was written and edited in-house, and it works offline once the app is installed.
