Redis misses are turning ordinary answer assembly into repeated database work.
Fast cited answers depend on cache reuse, while the release path must preserve live search traffic.
Who you’d be doing this for
“I had the sources open, then the answer just sat there while I was trying to compare updates.”
Stellan Korhonen · Independent Researcher
Uses cited answers repeatedly during time-sensitive web research.
What is at stake
Cache misses are pushing answer assembly past 900 milliseconds and loading PostgreSQL repeatedly. You must weigh a fast configuration rollback against a targeted release-path change that protects future backend scale.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- release velocity vs cache stability
- fast rollback vs durable release guardrails
- Redis reuse vs PostgreSQL headroom
- backend scale vs response predictability
Why Perplexity
Perplexity Search depends on rapid answer assembly for people researching current web information.
Written with these in mind
Not your kind of problem? 31 more at Perplexity, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.