Server stops responding for 10+ minutes each time there is a network seed hash upgrade (~2.8 days)
As the title suggests, I have observed such an instability pattern in xmrvsbeast.com. By quickly looking at the code, I suspect it is because the randomx algorithm implementation keeps switching the current seed hash between the old one and the new one, due to mixed share submission at a short period of time after the update, each costing seconds to finish and render the server unusable. But I'm not sure if it is the right cause.