Thanks for the thoughts.
I agree that it would be ideal if the hosting provider had their act together a little more. They seem to be struggling with some other aspects of their operation so moving providers is an option. (Lots of work and unknowns... but such is life).
I think I will try to move onto the 3.8 branch and see if thats more stable than 3.5.16. Currently my deployment of 3.5.16 is regularly dying with what I beleive to be runaway php processes related to both the cron tasks and caching/serving behaviour. Its an image heavy site and some of the images are just not being served in a reasonable time frame (minutes) ... while other times they turn up (eventually). PHP seems to lock up pretty regularly... less so when I disable the cron tasks.
I do not have enough information from my production system on my hosting provider to be able to pin down the issues so I'm going to move back to a loval dev server and see if I can get it stable.
Thanks.
I agree that it would be ideal if the hosting provider had their act together a little more. They seem to be struggling with some other aspects of their operation so moving providers is an option. (Lots of work and unknowns... but such is life).
I think I will try to move onto the 3.8 branch and see if thats more stable than 3.5.16. Currently my deployment of 3.5.16 is regularly dying with what I beleive to be runaway php processes related to both the cron tasks and caching/serving behaviour. Its an image heavy site and some of the images are just not being served in a reasonable time frame (minutes) ... while other times they turn up (eventually). PHP seems to lock up pretty regularly... less so when I disable the cron tasks.
I do not have enough information from my production system on my hosting provider to be able to pin down the issues so I'm going to move back to a loval dev server and see if I can get it stable.
Thanks.