Replies: 1 comment 1 reply
-
|
Usually having only the upstream engines enabled which you really need / want to use helps a lot. If that doesn't help you can look on the engine stats page to see which engines are slow and disable them. This should give you some insight in what might be slowing you down. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Thank you for some pointers. 👍 If other people have suggestion, be nice to post them here as a future reference. |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm wondering what are some of the best practices when it comes to improving performance and response time for SearXNG? I've not seen much discussion on it, and there are a lot of parameters to tweak. How are the best servers achieving sub-second response times?
Just to get a sense of how fast different sites where, I did some very rough testing estimates in my browser.
DOMContentLoaded timing in Firefox:
My own SearXNG server usually takes more than 6 seconds to process a basic request, any tips?
Beta Was this translation helpful? Give feedback.
All reactions