Here is the philosophical question, a question of process and flow...
I have a web application used for monitoring hundreds, maybe thousands of items non-stop using server-side functions; but currently the process uses a somewhat serial non-stop loop of individual ajax requests for each item being monitored and the loop is now taking too long.
Reworking towards a multi-threaded nature or sending multiple requests asynchronously in a better way; but here is the question... How to handle the main looping function?
I do not want to overload the server, asking questions when it's plate is still full or I can see creating a situation where the requests compound quickly and become a very, very bad thing. I also want to take into consideration some requests failing (hopefully not; but don't want them to be a wrench in the system).
So a user may... actually will... have their browser open 24/7 displaying a live view of everything being monitored at one-time on one-page and another concern is memory leakage and the like, so auto-refreshing the whole page every once in a while is also being implemented and looked into as well.
YOUR thoughts are appreciated.
(The technology and experience should not be key in this question but if interested, knowledgeable in and using elements such as php, jquery, json, apache, and mysql)