Kagi slow? Post here!

Vlad

For an update we are considering adding a new regional node in South America (Sao Paolo) and Australia (Sydney)

sm

Vlad A Sydney or Melbourne node would be nice, image search results are 3-4+ seconds here in Australia at the moment.

Vlad

sm Sydney node was aluanched on Thursday!

sm

Image search is unfortunately still so slow I've found myself avoding using it and defaulting back to using Google Image search.

sm

Thanks for the update Vlad , image search doesn't appear any quicker though, the time before the first image loads in any image search is still the same around 2-3s.

Fernandez

For some reason, I can't complete the run in my region.
For me, Tokyo, Seoul, Singapore, Hong Kong would be good.

naruto

Hi! Kagi started to feel quite slow today. Search results take up to 3s to show up. (I'm in Europe)

Vlad

naruto Has this been resolved for you?

naruto

@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:

Vlad

naruto 800-900ms is expected and is still considered very fast. Kagi has much higher quality results and gets data from many more sources than when you started using it 🙂

azu

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.

kagifeedbackz9qm0

From Switzerland :

MatthewSaw

Searching from Singapore

DensityInfinite

Posting from Australia.

MakeshVineeth

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 -

Dustin

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.