when you do web based code the web server has a set amount of time to complete the execution of the code by. Say its five seconds. Well one time when your server is not heavily loaded like when your developing five seconds is more than enough. But when you have a table lock or a heavily loaded server or a list of other reasons that can cause your web server to run slower than normal. Your code may not execute in the 5 seconds that it's allotted. There are several ways to reduce the likelyhood of this. Stronger server is one, better internet connection another but generally the best solution is to keep the data on your individual pages small and not complicated and insure all your sql queries use indexes and don't return very much data. The most frequent time I see this is say for exmple on an order page. When there are 20 orders its not a problem but when you get to 5,000 orders it becomes a problem. The way to do this is to give pages of info at a time. Say only 50 rows of the 5,000 orders. Then require the user to request the next page of data, then the next, and the next, etc.
|