4 ms·
I'm not saying to hammer down the refresh button. And yes there is a very good reason for it too work: in most scenarios the amount of concurrent connections t
by askmike 8y ago
I'm not saying to hammer down the refresh button.
And yes there is a very good reason for it too work: in most scenarios the amount of concurrent connections to the DB is at the limit. If you refresh once a minute later you're really not that much of an impact while the PHP instance might get the handle to the database needed to fetch the content. As a matter of fact, it worked for me with this exact article.
- nailer 8y ago> Try refreshing, eventually that worked > I'm not saying to hammer down the refresh button. OK. > If you refresh once a minute later you're really not that much of an impact If every user does this, the site now has 2x the amount of incoming requests.
- askmike 8y agoYep but twice the amount of incoming requests spread out over time. When the site doesn't load I think it's fair to do either 1 of 2 things: 1. Accept that you can't read the article. 2. Have some kind of retry mechanism ( for example: https://aws.amazon.com/blogs/architecture/exponential-backoff-and-jitter/ https://aws.amazon.com/blogs/architecture/exponential-backof... ) But I don't think trying once and complaining about it in a comment is making anything better for anyone.