Walaby
Sun 11th May '08, 11:30am
Okay, from what I've been able to read in the troubleshooting section is that one problem for database errors is the wait_timeout settings. It seems that the recommendation is the ensure the settings are at least 28800 (which is about 8 hours). I've been experiencing multiple database timeouts on my shared server, and Im sure this is one of the issues, but my host won't tell me my settings, and I don't have ssh access (Im leaving.. just hunting for a new host). It seems as if most, if not all shared servers are loath to set the settings so high.
My question is (and please don't take this the wrong way).. is this software more optimized for vps or dedicated hosts? It would seem with a vps or dedicated host, one has more control over the wait_timeout setting. I would have thought the code would be more efficient as to not need such a high timeout setting, but that's just a guess on my part. Again, not slamming at all, because I love the software... just trying to get it to work on a reasonably priced server environment is killing me.
Thanks
Mike
My question is (and please don't take this the wrong way).. is this software more optimized for vps or dedicated hosts? It would seem with a vps or dedicated host, one has more control over the wait_timeout setting. I would have thought the code would be more efficient as to not need such a high timeout setting, but that's just a guess on my part. Again, not slamming at all, because I love the software... just trying to get it to work on a reasonably priced server environment is killing me.
Thanks
Mike