| Freebase Dali |
01-09-2014 07:55 PM |
It's not an overloading issue. There's no considerable difference between regular members searching for new posts and regular members refreshing or navigating to different threads. It's all queries to a database via web request. If you have too many requests to the web server's connection pool or too many requests from the web application to its database, that will become apparent regardless of whether people are searching new posts or just navigating to new threads.
That wait stipulation is probably more in line with bot prevention. My guess anyway.
I don't know matter-of-factly, but it seems logical due to the fact that people searching for new posts would be not much worse than people simply browsing the website, in terms of web resource demand. Especially considering multitudes of people do just that as guests. Constantly.
As a user, it might be more demanding since the database has to be queried for multiple records, but it's not a logical preventative measure for a single wait when you are allowing a lot of people to execute that query or stored procedure simultaneously, irrelevant of whether they're doing it over and over again, which is less likely than a basic load of people just doing it once or twice every 30 seconds or so.
|
