- Edited
Kagi being slow (saw around 10s self-reported latency to US-WEST) tonight I doubt has much to do with latency to GCP, posting anyway.
Portland, OR metro, 97078
53
Kagi slow? Post here!
kandersonus A screenshot from the browser capturing query and including network tab in inspector would be useful in these cases.
I believe I caught the tail end of that production release which briefly caused performance degradation, wasn't able to reproduce for a screenshot after that was resolved.
All good now, just figured I'd share latencies re: OP. 
Thank you, Vlad!
For an update we are considering adding a new regional node in South America (Sao Paolo) and Australia (Sydney)
19 days later
Image search is unfortunately still so slow I've found myself avoding using it and defaulting back to using Google Image search.
a month later
For some reason, I can't complete the run in my region.
For me, Tokyo, Seoul, Singapore, Hong Kong would be good.
a month later
- Edited
Hi! Kagi started to feel quite slow today. Search results take up to 3s to show up. (I'm in Europe)
- Edited
@Vlad It got better, usually its now between 800ms - 900ms, which is still worse than when I stared using Kagi. Back then, I usually got <500ms responses.
I'm trying to convince my friend to use Kagi too, but he's a bit skeptical because it's not as fast as he expected.
Most recent Google Cloud Ping results:
25 days later
- Edited
The search result is clearly slower than Google.
It takes about 2.5 - 3.0 seconds to search for uncached data.
Edit: I was looking at the data from another time.
Kagi use event-stream(server send events) for display non-cached result.
It seems that the display is actually completed during the https://kagi.com/socket/search(event-stream) response.
/socket/search total response time is 2-3s.
But, It actually takes 1-2s seconds to display search result.
/search response example:
| Id | Time | Display |
|---|---|---|
| requestStart | 19:27:08.574 | Not Display |
| responseStart | 19:27:09.645 | ... |
| event-stream:0 | 19:27:09.663 | ... |
| event-stream:1 | 19:27:09.673 | ... |
| event-stream:2 | 19:27:09.684 | ... |
| event-stream:3 | 19:27:09.685 | ... |
| event-stream:4 | 19:27:09.685 | Display |
| event-stream:Close | 19:27:11.084 | Display |
| responseEnd | 19:27:11.086 | Display |
Research Snippet:
However, I have a feeling that the display is taking a long time because the white areas are displayed for a long time (1-2s).
Also, The current search page requires 2-RTT to display the results, so the latency may be doubled.
(/search page latency + /socket/search latency)
Firefox: 2461ms
Safari: 2540ms
Google: 858ms
From tokyo.
a month later
From Switzerland :
2 months later
Searching from Singapore
3 months later
Posting from Australia.
a month later
I've ran the following test in a personal laptop from Gurgaon, India -
This speed is pretty decent. However it feels really slow if I try to use Kagi on my corporate laptop which connects over a Always on VPN, this is the result -
From Vancouver, BC, Canada:
I would say that on a good day, Kagi is quite responsive but I think because of the nature of how far away most US-WEST servers are from Canada (and the lack of Google Cloud infrastructure in Western Canada), sometimes performance is all over the place.
21 days later
Kagi is 3x slower than Google in Spain.
Thx!