Replies: 2 comments
|
It seems Perplexica is demanding a ridiculous amount of context. In my tests, it's requesting over 600k tokens. But after I restarted the Perplexica Docker container, the exact same query worked fine without errors, with all the same settings. |
|
This feels like a classic capability-boundary bug where the system is constructing prompts as if every endpoint can tolerate the same context size. Once that assumption breaks, the failure is not really about the article itself, but about the absence of a size-aware preparation step before the request is made. A practical fix would be to push compaction or summarization earlier in the pipeline and make endpoint limits explicit in the request builder. That would turn an expensive hard failure into a predictable adaptation path. |
Uh oh!
There was an error while loading. Please reload this page.
I've noticed the Perplexica lacks awareness of the endpoints capabilities when it comes to context size. This often leads to 100k+ prompts which obviously wastes compute.
Reproduction is easy, just try to summarise something like an article by just starting a chat like this:
Summary: https://www.wired.com/story/the-technologies-changing-how-youll-watch-the-2026-winter-olympic-games/Response on openrouter from my docker logs:
For llama.cpp:
Same on server side:
Locally you could use context-shift but thats generally against the notion that clients should manage the contexts of their requests.
Are there any plans for the future to implement context compaction and reduction?
All reactions