/scholia

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem with response from web server #638

Open
fnielsen opened this Issue Jan 30, 2019 · 1 comment

Comments

Assignees
No one assigned
Labels
caching performance
Projects
  
To do in Meta
Milestone
No milestone
2 participants
@fnielsen @Daniel-Mietchen
@fnielsen
Copy link
Owner

fnielsen commented Jan 30, 2019

Sometimes Toolforge Scholia does not respond.

Wed Jan 30 09:26:20 2019 - *** uWSGI listen queue of socket 3 full !!! (101/100) ***
Wed Jan 30 09:26:21 2019 - *** uWSGI listen queue of socket 3 full !!! (101/100) ***
Wed Jan 30 09:26:22 2019 - *** uWSGI listen queue of socket 3 full !!! (101/100) ***

There are now multiple hits per second and some of these are likely bots (it is not possible to see from the Scholia log).

Perhaps we should switch to noindex.
@Daniel-Mietchen

This comment has been minimized.

Sign in to view
Copy link
Collaborator

Daniel-Mietchen commented Feb 1, 2019 •
edited

At such rates, maybe switching the non-landing pages to noindex is indeed necessary, at least as long as we do not have caching.

Can you see their paths? I would imagine them to start from the example pages and then make their way through whatever is linked from there and so on. Or do you see specific pages spike due to such usage?

@Daniel-Mietchen Daniel-Mietchen added caching performance labels Feb 1, 2019

@Daniel-Mietchen Daniel-Mietchen added this to To do in Meta via automation Feb 1, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment