Hi Michael!
Thanks for the warning! I'm not sure what kind of virtualization we're on.
But probably it also has this problem, as they say that the usual amount is
4 cores per server.
I guess the performance suffers more with full load (which is rare in this
case).
Still, even it it doesn't
Hi Majo!
Thanks again for your help.
Actually right now the server works with 3 pm2 instances on 4 CPU cores and
6GB RAM. Not too fast, but still not choking.
I also blocked Amazonbot (10-20K connections a day) and a couple of less
active bots. It helped a lot.
Looks like 5-7 instances is
Hi Andrew.
Glad I could help.
Certainly heed advice from Michael and don't overdo it with the instances.
Your issue was that there was a single one.. that will never be enough.
But 5 might be, or 7.. Impossible to say. 11 appears to be too much.
Now that you know how to set it, perhaps try
Kia ora,
We attempted using EZproxy in combination with IPAuth on DSpace 7.6 a couple of
months back and it didn’t work. A very quick test today though did seem to work
– not sure what changed!
In my quick test I did get a 500 error when downloading a bitstream – but it
also went ahead and
Thank you very much for your valuable suggestions and for pointing me
towards the SEO guidelines for DSpace 7. I greatly appreciate the effort
you and your team put into maintaining these guidelines
I will thoroughly review the guidelines and also follow the Google Scholar
troubleshooting
