As we get closer to Thursday, I still vote for Kristen's proprosal even if this code error gets fixed. Unless the host changes attitude, I'd like more responsive service, and I think that requires larger sums of money.
Never send a minion to do a god's work.
Glory ,'The Killer In Me'
Buffistas Building a Better Board
Do you have problems, concerns or recommendations about the technical side of the Phoenix? Air them here. Compliments also welcome.
helentm - Oct 29, 2003 10:19:51 am PST #5851 of 10000
Religion isn't the cause of wars. It's the excuse. - Christopher Brookmyre
Cindy - Oct 29, 2003 11:40:58 am PST #5852 of 10000
Nobody
If this error is (as it seems to be) a MySQL bug, I sort of resent us paying (or having the Buffistas chip in the lion's share towards what amounts to) a 100% increase, just to get a response from our ISP (not Kristen, IH--Kristen sweats blood for us)--especially if all we're asking for is for him to reset the daemon when this bug kicks in.
I realize the bug isn't his fault, but it sounds like it isn't our fault, either. Kristen, have you heard from Steven?
Jon B. - Oct 29, 2003 11:49:52 am PST #5853 of 10000
A turkey in every toilet -- only in America!
a 100% increase
1000% increase, actually.
DXMachina - Oct 29, 2003 11:53:39 am PST #5854 of 10000
You always do this. We get tipsy, and you take advantage of my love of the scientific method.
I realize the bug isn't his fault, but it sounds like it isn't our fault, either.
It is our fault in the sense that we selected MySQL for our system, which means we would have this problem where ever we were hosted. I can see Steve's point of view. We chose to use the software with the bug in it, and if that choice requires extra attention from the host, then we need to pay for it.
Kristen - Oct 29, 2003 11:59:07 am PST #5855 of 10000
I haven't heard back from Steven. I just poked him a little while ago about it. For all I know, he's on a rooftop somewhere manning a garden hose.
As for the rest, I really don't see the point of having this conversation again. You guys should make whatever decision you feel is best for the community but staying here in this current configuration is not a long term option, unless you're willing to live with the error messages.
Rob - Oct 29, 2003 12:11:09 pm PST #5856 of 10000
It is our fault in the sense that we selected MySQL for our system, which means we would have this problem where ever we were hosted.
No, we'd only have this problem at places that use the MySQL per-user connection limit as a way of limiting server resource use for shared hosting. Not all hosts do it that way.
Netgate just gives you a CPU/memory limit and you get an error from in your browser if an attempt to load a page exceeds the account limits.
Dreamhost has this conuries system, where you don't have a limit but you pay more a a lot extra if you exceed your allocation. At our rate of use we'd be their favorite customer, but that's another issue.
So moving to another shared hosting situation isn't necessarily going to put us in this situation again, but I think the stress for the stompies would be much less with a dedicated server. They wouldn't have to worry that each small change to the Phoenix code might put them in dutch with the host.
Astarte - Oct 29, 2003 12:16:58 pm PST #5857 of 10000
Not having has never been the thing I've regretted most in my life. Not trying is.
They wouldn't have to worry that each small change to the Phoenix code might put them in dutch with the host.
And, that will cost more money, but not necessarily 1000% more.
Kristen - Oct 29, 2003 12:18:07 pm PST #5858 of 10000
Just heard back from Steven. They've scheduled a shutdown/restart for 11:00 pm PST tonight so minimize the impact on other sites' traffic.
Wolfram - Oct 29, 2003 12:35:46 pm PST #5859 of 10000
Visilurking
Steven's the man!
Cindy - Oct 29, 2003 12:42:04 pm PST #5860 of 10000
Nobody
1000% increase, actually.
Frelling maths. Thanks, Jon.