Search Taking too much time to show results

Himalaya

KagiForMe I would also request the same @Vlad

Zac, on discord, mentioned that he may have found an issue and fix will be out in few hours. I will test it out when it’s out.

Vlad

Himalaya In your case there is something between our server and you that is slowing down the traffic it is not clear what.

From your screenshot, Kagi generated response in 0.8 seconds and normally this takes about 100ms to reach back the client.

What does your latency say here (in Kagi sidebar)

Vlad

KagiForMe We did push out a fix for this today.

KagiForMe

Vlad The fix worked great, thanks!

Himalaya

Vlad

Himalaya

I have attached the screenshot with latency, how do I check what may be affecting the response time? If you can guide me as to what may be affecting I can look into that

Himalaya

@vlad my Firefox is labelling the the requests as a slow response from server.

Fernandez

Experience around 2 seconds empty screen delay before showing search results.

This should have only started to appear in the past few days. I feel that I have not encountered this delay before, because the two-second delay is quite obvious.

What I mean by empty screen:

I have tested in chrome with a brand new chrome profile, no extensions. I registered a brand new Kagi account with default configuration for the test.
Chrome Debug Window Screenshot:

The slow package (highlighted with a red square) is a GET request to "https://kagi.com/socket/search?q=test&nonce=..."

I have also tested in Windows Firefox, Android Chrome, Android Waterfox. The results are the same, around 2 seconds delay before showing search result.

Vlad

Fernandez Can you share if this made it better for you and if not what region are you in and what is your latency to our servers ? (found in Kagi slide in sidebar, when you press top right icon)

Himalaya

This seems to be related to: https://kagifeedback.org/d/2986-search-taking-too-much-time-to-show-results

KagiForMe

Yeah, this is what we are all expriencing.

z64

Hi all,

We rolled out some tweaks for what may of been the issue in this case. Let me know if you see any improvements or have other issues still.

Himalaya

z64 is the fix in? Because I tried few searched and I am still facing the same issue? Do I have to logout and re login?

KagiForMe

z64 Definitely better, not perfect. It is now consistently approx 0.8 seconds, whereas before it was approx 1.8 seconds. Thanks for the work!

Vlad

KagiForMe 0.8 sec is generally what we aim for across the board, can not get much faster than that.

Fernandez

Vlad Better now, thanks.

Fernandez

Vlad
Actually, I discover the 2 second delay again. The slow package is still the GET request to "https://kagi.com/socket/search?q=test&nonce=..."
FYI: my IP is in US; latency to your server is 250ms

Vlad

Fernandez Occasional 2s may happen and is very hard to debug (maybe your network glitched..?) If there is consistenty latency issue that you can reproduce at will, that is something we can look more deeper into with you.

Horta

Kagi: 782ms to render the results

Google: 265ms to render the results

The difference is consistent across multiple trials. I've compared on Safari, Firefox, and Chrome and the conclusion is the same.

Kagi: about 590ms between the first paint and the paint that renders the results

Google: about 65ms between the first paint and the paint that renders the results

I've the exported the profiler data that I can share in case it is necessary.

Let me know what your information you need to debug it.

I've expected that Kagi would render the search results faster than Google.

Luis

Horta Thank you for your feedback. Our search results may sometimes load slower than Google's due to specific challenges. But we are actively enhancing our system to become the fastest for all queries. Please stay tuned for updates on that front soon!

« Previous Page