The host for Juicy Studio pulled the plug due to bandwidth usage. The new Juicy Studio is hosted on an Apache server, and the scripts are slowly being converted from ASP to PHP.
Author: Gez Lemon
The original hosting company for Juicy Studio, http://myhosting.com, effectively kicked me out for using too much bandwidth. I know nothing about hosting, so asked for help in selecting a good host. I was absolutely amazed by the massive response I received, and am very grateful for everyone who sent an email with suggestions. There were so many, I'm still in the process of trying to reply to them all. In particular, I would like to extend a special thank you to the following people, whose generosity helped me through a difficult time (by surname in alphabetical order).
- John Allsopp
- Pamela Berman
- Douglas Clifton
- Derek Featherstone
- Andrew Girdwood and all at www.bigmouthmedia.com
- Patrick H. Lauke
- Mike Pepper
A few of the emails were from people in a similar situation to me, and asked if I would publish the host I finally choose. I finally chose Pair Networks, suggested by John Allsop. The bandwidth and hosting costs are very reasonable, and my experience with them so far has been very pleasant.
One of the things that became immediately obvious from the recommendations, was that Apache is a better platform for shared hosting than IIS. I think the reason for this is probably due to the memory leakage due to bad programming practices. It's good practice to release any memory allocated when creating objects on a server, but a lot of tutorials miss this out because it's taken care of automatically by the operating system. What they neglect to take into account is that the memory management process runs in a low-priority thread, and on a busy server, the low-priority thread doesn't get a look in. Eventually, the server doesn't have enough memory to operate, and resets itself, but not before a severe degradation in performance which can last a few hours. If all programmers on a shared server released their resources, there wouldn't be such a problem with IIS. I'm assuming that Apache is better at memory management than IIS.
Consequently, I've had to rewrite all scripts from ASP to PHP with MySQL. I've only had a very brief look at PHP in the past, so it's been an interesting learning curve. I'm slowly transferring the information from the old site to this one, but severe lack of time is causing a problem. I was away on holiday when Juicy Studio was halted by myhosting.com, and straight back to work when I returned home. This weekend has been the first opportunity to do anything, but I'm happy at least something is in place. I've ported over all tutorials written by someone else, and will begin to port other articles over during the week. Once that's done, I can get the services in place, and hopefully, things will be back to normal. As this is my first PHP site, there may well be problems. If you spot anything, please let me know.
Thank you to everyone who sent an email with an offer of help, it was very much appreciated.