53
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.

                  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)

                    • sm replied to this.
                    • sm likes this.

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

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

                            6 days later

                            sm Sydney node was aluanched on Thursday!

                            • sm replied to this.
                            • g4k likes this.

                                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.

                                  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

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

                                    • Vlad replied to this.