It depends on how often you need to update the data on the front panel. Most pages do not need to be constantly updated. I don’t know that there is a threshold of “best practice”, but I think a good starting point would be 15-20 second updates using Ajax. Make your Ajax calls fast and thin - maybe just return empty if there are no updates. If you need faster updates, look at what is called long polling
. Long polling is basically where you call the ajax call to the server, and the connection is open until the data is sent. A long poll will take up more server resources because you will have open connections and threads while they wait for the data to be ready. With ASP.NET, you also have to worry about killing long polling streams, because by default these streams will not be killed when the browser closes the connection (for example, if someone moves away from the page.)
source share