Skip to content
This repository has been archived by the owner on Sep 7, 2023. It is now read-only.

Inaccurate statistics #199

Closed
dalf opened this issue Jan 22, 2015 · 2 comments
Closed

Inaccurate statistics #199

dalf opened this issue Jan 22, 2015 · 2 comments
Labels
enhancement

Comments

@dalf
Copy link
Contributor

dalf commented Jan 22, 2015

the /stats URL shows different numbers when the page is refreshed.

Explanation (I guess) : the statistics are calculated per process (with uwsgi at least).

It's not a big issue except (perhaps ?) for the error counts.
@pointhi
Copy link
Contributor

pointhi commented Jan 24, 2015

I think we can fix that if we are using a database instead local variables to store the stats.

Furthermore, a restarted searx-engine can build on the previous data like score.

@asciimoo
Copy link
Member

Collect stats related improvements/ideas to #162

@pointhi pointhi mentioned this issue Jan 28, 2015
Closed
@dalf dalf mentioned this issue Feb 18, 2015
Closed
@dalf dalf mentioned this issue Dec 25, 2015
Closed
dalf added a commit to searxng/searx-space that referenced this issue Jan 5, 2020
@dalf
[enh] self-report: check if an engine has returned some results since…
f303c4f 
… the instance has started.

Check "Number of results" in the /stats page.
The /stats page is loaded multiple time because of possible use of uwsgi
see searx/searx#199
@dalf dalf mentioned this issue Jan 28, 2020
Open
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@asciimoo @dalf @pointhi