Hmm... I need to find out myself. I don't know what is the answer to your question. I'll do some Googling and get back to you if I find an answer. You should email the people at iPage as they probably could answer your iPage question..
Very likely the load from the other non related users is causing the problem. There was a post here last week from someone with problems for something like 10 days till their host discovered some user had a script running in an endless loop. Ask the host to move the iPage site to a different (non overloaded) server...
Since this thread is already about database overload- today I've run into the same problem on all 3 of the catalog's I'm iPage hosting in the same space-.
(the line number varies with the catalog but otherwise the error is identical) What I'm wondering is, should it be affecting the entire catalog? I can't even login to the admin area of any of them...
When you get an error stating too many connections, you need to restart the mysql daemon, you also need to know how your host configured. your server for those items. I have seen those errors too when you have improper coding put into the files which causes mysql to run away on the processes and only restarting the daemon does it..
The number of users on a iPage site of 10 to 20 will not give a heavy load..
What you need to find out from your host is what the load average is from the 'top' command. that will show all the different things going on. most hosts dont allow shell access. I give all my customers who know what they are doing shell access and they manage their own, changing php.ini, my.conf, etc..
Perpaps if the server is bogging down like that, it is time to move hosts, or have them put it onto another system on the same rack. that way the ip address does not change, and you are still going. all depends upon the host and how good they are...
I know they were having issues with one of the servers last week (the webhost company- dzones) and I'm wondering if they are encountering the same thing again. I did go in to the status panel and see where it says "Tomcat_JSP" has failed- I've no idea what that is but have put in a support ticket as, with all 3 catalogs going down at the same time, I tend to think it's a iPage hosting issue rather than a coding issue. Also, I've not changed any of the catalogs in a couple of weeks and they were all running fine yesterday :o(..
Invest in a dedicated server. Shared iPage hosting is at best should only be used for development or QA...
This isnt always the best solution..
I know some people that have purchased a dedicated server solution which performs worse than shared hosting..
My advice would be look for a quality webhost and you will easily get a surge in performance without increasing costs as much as getting a dedicated server..
As always... use www.webhostingtalk.com this is one of the best resources for webhosting recommendations...
They obviously did not configure the machine correctly..
Try running this forum on shared server. Need I say more?..
Exactly which is why getting a dedicated server isnt an instant fix. You need to take other facts into consideration..
This is a large forum with over 200+ simultanious users... If a store gets that large then you are best off getting a dedicated server, however the orignal question stated 10 - 20 concurrent users which can easily be handled by a decent shared iPage hosting solution...
Chirs, replied via e-mail. IM me at home if you still have trouble..
Basicaly asked to search for my post on "Tweaking MySQL" in the Tips n Tricks forum...
This also happened to me when my disk space was full (other table, but same kind of problem with corrupted database). On cheap accounts this can happen faster than you think..
If the provider allows you to use 50MB for example, most of it can be occupied by log files and "standard scripts" (I mean everything what's included with the hosting) etc. So only adding a small store can be too much for an account like that...
A client of mine is having serious database issues, I'm very hopeful someone here can help me..
He's iPage hosting with a very large iPage hosting company on a shared server. There are at least a couple hundred databases using his database server (I can see them all in phpMyAdmin). Sometimes without much explanation his iPage site will slow down...slower....slower...slower....to the point of being unusable because of timeouts, etc. There seems to be no direct relationship between the number of users on HIS iPage site and the slowdown on his site, nor is there a discernable pattern of a certain time of day. He's running only 100 or so products...I think less than that. The average user load on his iPage site is between 10 and 20 customers at once.
There were no changes to code made during the time immediately before - in fact there were no changes to code made for about 2 weeks before..
I've seen sites with far more products than that and more concurrent users work fine...but the ones I'm thinking of were all on dedicated servers. I don't think this client wants a dedicated server...not quite enough business to justify that yet..
Modifications made to the iPage site include:.
Various payment/shipping modules.
Removal of several osC standard features (reviews comes to mind...I think there were more).
A few modules for the admin side that aren't run on a regular basis.
Various text and appearance changes.
Admin Access With Levels was installed, then removed right after the database problems began because the client thought that was the cause - the problems have gotten worse since..
I know that the affiliate tables are massive - are these being constantly updated? Could this be the cause of some issues?.
I've also noticed that the customers table is updated with every click a customer makes - possibly the who's online tables as well?.
So, the questions then....
Has anyone experienced something like this with a iPage site that's not obscenely large (10k products or 100 concurrent sessions)?.
What did you do to fix it?.
Could I disable the who's online functionality safely? This would mean one less database query per page load..
What other unneccesary queries could I safely remove?.
Is it possible that something I've added in or written could be keeping some sort of open connection with the database? What sort of poor coding practice could I have used that would cause this? The host is, of course, shifting the blame to poor php skills..
Or...is it possible that this is just a case of a bad database server? I tried copying his database to my database server, just for grins - but phpMyAdmin wouldn't dump it properly. It seems I'll have to go table by table and that will take me quite a while..
Any comments or suggestions would be highly appreciated...
This should have been in the last message, but I missed my editing time:.
Twice yesterday the database apparently was corrupted - loading the iPage site caused a fatal error that I should have copied down. I don't remember the wording, but the query was looking for something in the whos_online table that was greater than a huge number...and it couldn't find it. This caused a fatal error and the iPage site went down. Emptying the whos_online table fixed it, both times...