-
Notifications
You must be signed in to change notification settings - Fork 7
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
Load test: sending to lobid-resources subject inboxes #986
Comments
Wrote a gist https://gist.github.com/dr0i/72fdc385fc4e72a6930f1644523bbdc6. |
https://test.skohub.io/ is up now, see skohub-io/skohub-pubsub#12 |
Up'n running. Crontabbed starting every day at 09:00. |
Just a heads-up for @literarymachine: https://test.skohub.io/ should start receiving automated traffic starting tomorrow 09:00, see #986 (comment) (first comment in this issue). |
@literarymachine @fsteeg it's already started and sending. And will , from now on, start every day at 9:00. |
Talking to @literarymachine at ELAG2019, he said that it would make sense to make the load test a bit harder by sending out all the notifications at once as soon as the daily updates are in. Reopening to test this scenario for some days. |
Removed the |
I haven't closely monitored the server, but it is still up and running. Thinking about this, I should probably add some logging: skohub-io/skohub-pubsub#14 |
Why not both? |
Is this running test actually useful or can I stop if it's indeed unnecessarily producing load? |
I guess you can stop it for now. |
@dr0i have you stopped the load test already? I not, please do and close this issue when it is stopped. |
Yeah I stopped it already at 11th July. For reference, it can be started again enabling dispatchLobidResourcesToSkohubInbox.sh, see crontab. Closing. |
https://test.skohub.io/inbox?target=http://test.lobid.org/gnd/4020517-4
While we don't have a live system behind lobid-resources, the idea here is to simulate the load created by multiple senders. To increase the amount of messages, we could change this from subjects to authors in the future.
The text was updated successfully, but these errors were encountered: