Kagi slow? Post here!

sm

liamstevens Did anyone get to the bottom of this slowness?

I find Kagi better than Google or DDG in every single way except this weird delay returning results 😅

Vlad

sm There should not be any slowness anymore.

If you have it please record a video of what you experience, with the network tab in the browser open and share your region so we can start debugging it.

sm

Vlad here's a video with the network tab open with a 2-3 second search, then a quick search, then another 2-3 second search.

This is on a wired Ethernet connection with 1000/50Mbit internet, 2021 Macbook Pro M1 Pro, Firefox 101, location is Melbourne, Australia

sm

sm @Vlad FYI Kagi is a lot faster this week!

My searches have gone from 3-4s to 1-2s at most.

Vlad

sm That sounds better, thanks for reporting back.

sm

Vlad it could just be because it's launch day but it's back to being slow - slower than ever actually, in an unrelated bug report you can see how long even settings take to load.

This occurs both on very strong wifi (wifi 6, maximum bars) with gigabit (ipv6) internet and on 5g speed testing 200mbps.

Vlad

sm We did have some issues yesterday. How is it looking now?

sm

Vlad unfortunately still painfully slow to load and load responses.

Here are two videos comparing Kagi and Google - that doesn't have the performance issues:

Here is a Speedtest taken on the same connection and device: https://www.speedtest.net/my-result/i/5141669568

The latency to Kagi seems very high too:

However GCP latency looks ok:

Update - latency to Kagi seems to have dropped to around 550ms but the search performance is exactly the same.

Vlad

sm We have located the cause of the problem in the meantim and are working on a fix. It seems the latency is about 1.5 more than it should be, sorry for that.

sm

Vlad well done! I'd be really interested to know what it ended up being if that's something you'd be able to share when it's resovlved.

Vlad

sm We had to talk to master db to check billing info. it was located in US. So there was a roundtrip to it from ASIA. We now run regional read replicas eliminating this.

sm

Vlad that's made a very noticeable difference.

Searches now average between 1 and 2.2 seconds both on Firefox (desktop) and Safari (iOS).

Thanks for letting me know what it was too, always interesting to hear the cause of things like this!

Vlad

sm Mobile results seem like faster than 1s? can you record a video of desktop results with network tab open if they still seem slow?

sm

Vlad Yeah it's a bit of a mix between 1s - 2s from the point where you git return/search to the results loaded which is good.

The first video in my post is in Firefox desktop with the network tab open, also returning between 1-2 seconds which is good.

No complaints from me, well done fixing it.

Vlad

Sorry I missed the first video. Looking at it results,appear snappy, subjectively feeling faster than 1s. if it was 2s that would be cause for concern. Challange with AU is that it is faster to retrieve results elsewhere (Singapoore) and fiber-ship to AU then to search the web directly in AU.

Can I ask you a favor. Can you side by side load a couple of results in DuckDuckGo and Kagi (network tab not needed)? @sm

sm

Vlad it's looking really good, only had one slow response ("good music"):

(don't judge me for my silly example searches 🤣 )

Vlad

sm Thanks for doing this. Is it fair to say that Kagi feels 20%-50% faster than DDG on average in AU ( with the exception of that one query when it seems to have gltiched)?

stonekyx

Connecting from Tokyo.

I know this issue has been closed, and I do see good performance when searching normally (about 1 second in most cases).

But there is an "edge case" which makes it very slow for me (feels like 3-4 seconds) - If I add a URL parameter &r=no_region to temporarily search without a region. I bookmarked this URL and gave it a shortcut so that I can get international results when needed, but it's apparently much slower than just normal searches. Not sure if you have looked into such cases before.

Vlad

stonekyx Edge cases are probably not network latency related, but you hitting a specific query. Next time that happens pleae mark that query and open a new post about it so we can investigate.

We do not currently have a DC in Japan, and the closest to you I think will be asia-east2 Hong Kong so this will probably add _100ms latency.

« Previous Page Next Page »