One of our ashram websites was becoming very slow to respond, and one of us submitted a ticket to Nettigritty. I interjected with the following comments, when Nettigritty responded that they did not see any issue:
In general, these shared web servers will not be very responsive - you might have seen how slow the web control panel is. So, if the mysql server is also on a shared server, or on a shared network connection like our cyberoam, that may be the reason.
The solution may be to use asynchronous protocols instead of real time updates, or using larger time-out settings on the server, or using protocols which run over http/https like xml / soap. (But SOAP has been deprecated.) In general, it is very dangerous to directly leave the sql server open to the web.
In general, these shared web servers will not be very responsive - you might have seen how slow the web control panel is. So, if the mysql server is also on a shared server, or on a shared network connection like our cyberoam, that may be the reason.
The solution may be to use asynchronous protocols instead of real time updates, or using larger time-out settings on the server, or using protocols which run over http/https like xml / soap. (But SOAP has been deprecated.) In general, it is very dangerous to directly leave the sql server open to the web.
No comments:
Post a Comment