53

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

  • sm replied to this.

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

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

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

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

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

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

                              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.

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

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

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

                                    • Vlad replied to this.

                                        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)?

                                        • sm likes this.
                                          2 months later
                                          7 months later

                                          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!