Well, even if it turns out that the problem is a bug in MySQL, I can't see his stance changing on that. Other sites using MySQL don't seem to be affected by this bug the way that we are. His only option would be remove the restrictions on connections and I'm thinking that's not going to happen.
Joyce: Dawn, you be good. Xander: We will. Just gonna play with some matches, run with scissors, take candy from some guy, I don't know his name.
'Beneath You'
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.
Kristen - Oct 28, 2003 12:35:31 pm PST #5838 of 10000
§ ita § - Oct 28, 2003 12:35:57 pm PST #5839 of 10000
Well not canonically, no, but this is transformative fiction.
Astarte, we're only allowed 100 connections. And if we increase it, we'll just falsely eat more, I bet.
We're currently all sharing ONE of our allotted 100. The system is just bogarting the other 99.
Astarte - Oct 28, 2003 12:36:52 pm PST #5840 of 10000
Not having has never been the thing I've regretted most in my life. Not trying is.
K. Shutting up now.
§ ita § - Oct 28, 2003 12:37:12 pm PST #5841 of 10000
Well not canonically, no, but this is transformative fiction.
if it turns out that the problem is a bug in MySQL, I can't see his stance changing on that
Not even restarting the daemon?
I wish I knew what the timeline to a bug fix was, but it's not something we can use as a factor in decision making.
We may need more than $20 of resources, but a bug in mysql making us need $200? Yikes.
edit: Astarte, any fruistration in that post was not directed at you, just the situation
Astarte - Oct 28, 2003 12:40:25 pm PST #5842 of 10000
Not having has never been the thing I've regretted most in my life. Not trying is.
Understood, ita. I just wish I knew enough to be helpful instead of a parrot creature.
Kristen - Oct 28, 2003 1:05:33 pm PST #5843 of 10000
Not even restarting the daemon?
He's going to talk to his server admin about that. But it's not really a long term solution since we'll most likely start to creep up again on connections.
ETA:
We may need more than $20 of resources, but a bug in mysql making us need $200?
I've already had one person who was willing to move a site over contact me. Maybe a few other people who are interest could email me and we'd have a better idea on what the monthly cost would work out to be for you?
Sean K - Oct 28, 2003 1:15:07 pm PST #5844 of 10000
You can't leave me to my own devices; my devices are Nap and Eat. -Zenkitty
As soon as I get a new job, I'd be interested in picking up a domain name, and starting a site for myself. I'd do it with FG on the server we used. I don't know how soon that will be, though.
Astarte - Oct 28, 2003 1:17:09 pm PST #5845 of 10000
Not having has never been the thing I've regretted most in my life. Not trying is.
But we'd still be on the hook for the $200. If, for example an account that moved over left (for whatever reason) we would be financially responsible. I think we have to plan on that basis as a business issue (for lack of a better term). If the expense can be defrayed, great, but if we rely on that and it doesn't pan out, that's not good for long term fiscal health.
Kristen - Oct 28, 2003 1:26:22 pm PST #5846 of 10000
No, I understand that. I'm just saying that if we only have two people who are seriously interested, maybe it's not even worth further discussion. If we have 10 people, it might be worth a try.
Cindy - Oct 28, 2003 2:59:29 pm PST #5847 of 10000
Nobody
Kristen (correct me where I'm wrong, please), I seem to remember that after a past crisis, and/or after ita shut off the RQG, and we pared down our threads, we were using well under 50 connections. If this problem is a MySQL bug (which I realize isn't Steven's fault), we're not actually problem children. We're victims of the bug. Given what's going on, shouldn't Steven resetting the daemon be part of the support he provides as ISP?
I'm in way over my head, so where I sound terse, please read it as me trying not to screw up. I just don't understand why we'd upgrade, if this is a MySQL problem, and not a Phoenix!Code problem, and I don't understand why you're saying our usage would creep up again, if we run under the 50, when we're not afflicted by the bug.