Replies: 3 comments 2 replies
-
|
I'm not sure to fully understand, but with 1 second budget, some engines won't have to time to process the query: they will time out from the SearXNG point of view. You can set the max timeout to 1 second on the server: Line 161 in b3d29cb Also, there is an undocumented (?) feature: you can set the max timeout per query For example:
See searx/searx#1640 (comment) for the details. |
Beta Was this translation helpful? Give feedback.
-
|
Didn't ever know there is an |
Beta Was this translation helpful? Give feedback.
-
|
You can disable some engines and just keep one. |
Beta Was this translation helpful? Give feedback.
-
|
Not are engines, is how to works the searxng because no works at hight velocity at low load and at hight load for example 99% cpu works fast |
Beta Was this translation helpful? Give feedback.
-
|
I want low latency in searxng at low load because searching intermittently is faster and results are displayed in 1 second (i.e. at high load) on average instead of 3 or 2 at low load. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Our Searxng latency is pretty good. 1 sec on average, 2 seconds for our P99 latency. But we want to make the P99 latency 1 second as well, even if it means less comprehensive results.
Anyone have any suggestions for this?
Beta Was this translation helpful? Give feedback.
All reactions