'Safe'
Do you have problems, concerns or recommendations about the technical side of the Phoenix? Air them here. Compliments also welcome.
The simplest thing to do (and oh! look! it's a weekend!) is to run through the code and put explicit closes after every recordset is done with.
That's phase 1 of the process.
The second phase, is to actually run through the code and squeeze down the queries. This has been, she says sheepishly, on my plate for a while. Anyone want it?
ita, I'd be the first to volunteer had I any idea what's going on. I'm even working all nights all weekend and will be bored.
ita, I'd be more than happy to help out in any way I can -- I haven't a clue if my PHP/MySQL skills are up to where I'd understand the Phoenix code if I saw it, but I can certainly try.
Perhaps fangeek can turn on mysqld logging (for a short period of time) so that we can get a handle on what's happening?
IH informs me that, while they did not anticipate any problems with the site, they simply weren't expecting "over 200 concurrent mysql connections at the same time". They had no way of predicting that. They informed us that we are the reason the server has been so slow of late. They also suggested that we modify our code, as they believe the script we're using is the problem.
IH mentions that they think if we "optimize the database queries" that will help a lot. It isn't our bandwidth usage that is the issue, it's our resource usage.
I gotta say that IH actually giving us a clue as to what's happening is much better than the way HR just kept telling us "You should have fixed your code."
Hey, I'm where Jess is. I've been out of the programming loop for a while so I dunno if I'd be any help, but sql used to be my baby, so I'd be happy to at least look it over. I'm limited as to my online time, but if I could look at the code offline I'd have a fair whack of time this weekend to do it up. Let me know how to do whatever I gotta do. Like I said, I dunno if I'm up to scratch but I'd be glad to be extra eyes and hands.
I have an ERD lying around here somewhere. I'll make sure it's up to date, and then outline the queries involved in each transaction.
I think that's simpler than learning to read the code.
Sorry, I had to run off and do work for the people who write my paychecks.
Perhaps fangeek can turn on mysqld logging (for a short period of time) so that we can get a handle on what's happening?
I have asked this question. Will let you know what I hear.
DX -- I've taken off Natter 9 and Bitches 1. I didn't miss any, did I?
Nope. I've been working on Bitches 2, but it won't be ready for a couple of hours.