My web server "times out" when trying to process a very large number of bookingsEvery web server has a "time out" setting - a time after which running processes are automatically terminated if they're still running, in order to protect the server's resources. Typically servers have this set to around 2-5 minutes - more than enough time for most operations!
If, however, you have a slow performing/heavily loaded server, and attempt to perform a very large task - such as modifying a vast number of bookings in one go, this has the potential to exceed your server's timeout period (although reports of such occurrences are extremely rare).
There are a number of ways you can combat this:
- The easiest way is to simply reduce the amount of bookings you're attempting to add/modify/delete in a single action. For example, if you need to add a booking to every single calendar date for the next two years, and you find the operation "times out", consider splitting such operations into two, and add half the bookings at a time.
- Reduce the number of "watch notifications" in use. For example, if your users have set up "watches" to receive email notifications whenever bookings are modified, and you then attempt to modify a large number of bookings in one go, MIDAS potentially has a lot of email notifications to send, which can slow down the overall speed/performance, especially if you have a slow SMTP server/email gateway.
- If you have access to your server's configuration, consider increasing the server's timeout period as necessary.
- Consider upgrading your server/network speed, or relocating MIDAS to its own server. Running MIDAS on its own server will mean that more server resources can be dedicated to your MIDAS, and traffic/resources won't have to be shared with other sites/applications.
← Return to Knowledgebase