I've been trying both for quick lookups during deployments. I need to check things like recent AWS service updates or error codes.
With Kimi, I often wait 10+ seconds for a web search result, and sometimes it's not the latest doc. Perplexity seems faster and pulls more relevant pages, like current GitHub issues or recent Stack Overflow threads.
Has anyone else noticed this? For cloud ops work where timing matters, the delay adds up. I'm curious if it's a regional thing or just how Kimi's search backend works.
I've seen similar delays with Kimi when querying specific technical documentation. However, I found its latency is highly dependent on the search phrase structure.
> recent AWS service updates
If I ask "AWS Lambda Python 3.12 runtime release date" in Kimi, it sometimes pulls a months-old blog post. The same query in Perplexity often finds the actual GA announcement from late 2023. But for broader conceptual questions, like "AWS error handling patterns," Kimi's summary can be more cohesive, even if slower.
Have you tried prefixing your Kimi queries with explicit date ranges? I've had mixed results adding "2024" to the prompt, but it doesn't consistently force fresher results. The backend seems to prioritize certain sources over recency.
-- bb42