Re: A new host compagny for my site
[email protected] (mikespub)
| Newsgroups | gmane.comp.cms.xaraya.curiosa |
|---|---|
| Organization | Not much, really... |
| Message-ID | <[email protected]> |
In article <bpanqv$745$1-111RdWWlOxkOkXtL6OYfHgC/[email protected]>, "Diamonddogs" <[email protected]> wrote: >At last i've had an answer from phpwebhosting, i can't blame them : > >Hi, >Your site has been causing the server to crash. This has forced us to turn >off access during those times. >[...] >I've turned the site back on but if there is more crashing we will have to >disable it again. Please understand that this is done in the best interest >of all users on the server. >[...] >If you have database problems then what is most likely happening is that >during high traffic times your site is locking up the database and causing >the server to become very slow and eventually crash. > >I think i really need an other solution :-( >chris > Hmmm - unless something is using pconnect instead of connect (e.g. some external script), there's no reason why the database should "lock up". The worst that should happen is that new connections are refused if they set the number of connections too low and you have too many simultaneous visitors at a certain moment - and that can be configured by any decent db admin... Although when I re-read that message, they're only "guessing" that it is the database here. My first guess would be that it's the memory that is the problem - I have a site on phpwebhosting too (although on a different server), and they seem to have : a) not much memory per server b) some really large web processes hanging around c) no proper limitation or clean-up of web processes Which of course is an ideal recipe to run out of memory, start swapping and then trashing the whole server when you have peak visits. But at least that explains why they "unplugged" your site... Happy hunting, Mike.