Closed fsteeg closed 4 years ago
Wrote a gist https://gist.github.com/dr0i/72fdc385fc4e72a6930f1644523bbdc6. When https://test.skohub.io/ inbox is up, it may be crontabbed.
When https://test.skohub.io/ inbox is up, it may be crontabbe
https://test.skohub.io/ is up now, see https://github.com/hbz/skohub-pubsub/pull/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 https://github.com/hbz/lobid-resources/issues/986#issue-429332959 (first comment in this issue).
@literarymachine @fsteeg it's already started and sending. And will , from now on, start every day at 9:00.
Create #992 to be able to see what's happening. @fsteeg If this issue is good you can close it.
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 sleep
. This script will now work as fast as it can, I expect no more than 10/s.
Removed the sleep. This script will now work as fast as it can, I expect no more than 10/s.
I haven't closely monitored the server, but it is still up and running. Thinking about this, I should probably add some logging: https://github.com/hbz/skohub-pubsub/issues/14
To increase the amount of messages, we could change this from subjects to authors in the future.
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.