53

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 replied to this.

    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.

      8 months later

      Similar issue from another Tokyo user. Kagi searches in iOS Safari feel like 1 second of blank screen before results populate. This is every search. DuckDuckGo and Google are very fast. Using Kagi on the Orion iOS browser is much faster, but, as noted in another post, I cannot use iOS Orion as it freezes 100% of the time after minimal use.

      • Vlad replied to this.

        maikeru8 Sorry to hear that. This sounds like Safari/Kagi extension problem, not a Kagi latency problem. Can you try using Kagi on Safari through xSearch?

            Vlad

            I’ve installed xsearch, disabled the Kagi extension, activated the xsearch extension….but how do I force iOS Safari to search in Kagi? It’s producing results from the prior iOS default browser.

                From Japan as well -- both normal search and /html are 3+s which is much slower than ddg (~ 1s-1.5s) or google (~ 500ms-1s)

                Sorry for not taking a video, here's a screenshot of the network page with final timings instead
                normal version (search xhr almost 3s)

                and html version (first page load almost 3.2s)

                (note I didn't renew my subscription so these are on the '100 free searches' -- any chance that'd impact performance? I remembered it was slow and wanted to check speed again before resubscribing, as I'm really torn between the better results and the display speed...)

                Thanks for looking at these reports seriously!

                  g4k We isolated the cause for this and are looking into mitagiating it. In the meantime post any slow queries here.

                      17 days later

                      2.8s seconds for a simple query

                        Ok stand by. We plan to roll out some tools that will allow us to better debug this (with the ability for users to opt in into debugging logs)

                          a month later
                          Merged 7 posts from Kagi is generally slow, but this was the worst. 28 relevant results in 8.77s.

                            I've noticed recently (say - in the last few months) that Kagi seems slower here in Australia - especially image search.

                            Intermittently when searching (text) there is a 1-3 second delay before results are displayed.

                            When searching for images the increased load times are more pronounced and quite frustrating - so much so I've had to use another image search provider at times because I knew Kagi would take a long time to load.

                            Here is an example on a modern Macbook Pro with up to date Firefox and 1000Mbps internet connection with an ISP that has great peering locally and internationally.

                            • Connected to: ASIA-SOUTHEAST Network latency: 113ms

                            Screen recording:

                            When looking at the network requests Firefox notes that the server is much slower than the recommended response time:

                              Kuinox I ran this query again today, and it took again a significant time:
                              79 relevant results in 10.32s. 50% unique Kagi results.

                                  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

                                  • Vlad replied to this.

                                    kandersonus A screenshot from the browser capturing query and including network tab in inspector would be useful in these cases.