I'm getting an error on the links page:
August 3, 2003, 8:04 pm Jon B.[211]: ERROR [2] mysql_close(): no MySQL-Link resource supplied line 81 of file /home/bufforg/public_html/classes/giles.php
It shows up twice after every section header.
Don't let the space bugs bite!
Kaylee ,'Objects In Space'
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.
Jon B. - Aug 03, 2003 6:05:01 pm PDT #4506 of 10000
A turkey in every toilet -- only in America!
§ ita § - Aug 03, 2003 6:08:25 pm PDT #4507 of 10000
Well not canonically, no, but this is transformative fiction.
Whoops. Copied over one too few files.
Should be gone now.
§ ita § - Aug 03, 2003 6:11:27 pm PDT #4508 of 10000
Well not canonically, no, but this is transformative fiction.
You know, I wish I knew more about the internals of MySQL/PHP, to know where the break even point is between closing db connections before a script is over, and reusing just one connection for every query.
I guess it depends on the speed the script runs -- the faster it's done, the more likely keeping one connection open for the whole thing is the efficient choice. But if it takes a long time to run, the bits inbetween where it's not being used, but is just sitting there ... those'll add up.
Which implies that a faster machine works better for keeping them open all script long.
But I could be making shit up.
Elena - Aug 03, 2003 6:27:31 pm PDT #4509 of 10000
Thanks for all the fish.
So, according to your made up shit, would a slow machine be better than a fast one for, um, whatever it is we're trying to have happen?
§ ita § - Aug 03, 2003 6:31:08 pm PDT #4510 of 10000
Well not canonically, no, but this is transformative fiction.
I think the changes that have just been made are probably the best interim move for this machine. Streamlining the SQL period is best for any machine.
Tom Scola - Aug 04, 2003 2:56:04 am PDT #4511 of 10000
Remember that the frontier of the Rebellion is everywhere. And even the smallest act of insurrection pushes our lines forward.
I don't know a whole lot about PHP, but it appears that it has support for persistent SQL connections built in.
PHP: Persistent Database Connections
However, this page gives the cryptic warning:
Warning:
Using persistent connections can require a bit of tuning of your Apache and MySQL configurations to ensure that you do not exceed the number of connections allowed by MySQL.
It doesn't go into details about what exactly those configuration parameters are, and how to tune them.
Michele T. - Aug 04, 2003 6:24:13 am PDT #4512 of 10000
with a gleam in my eye, and an almost airtight alibi
I'm going to do a little research, and see if I can turn up any information on the matter, or even better, someone who knows something about the subject already.
§ ita § - Aug 04, 2003 6:57:20 am PDT #4513 of 10000
Well not canonically, no, but this is transformative fiction.
I think persistent connections are what we don't want. We're being told we have too many open -- not that we're opening too often. So persistent connections would leave us with more open, since we'd lose the respite when a normal connection is closed at the end of the script.
Kristen - Aug 04, 2003 7:40:56 am PDT #4514 of 10000
I thought the idea with persistent connections was that we had, say, 50 always open and every task used those 50, instead of opening and closing a connection each time the database is accessed.
§ ita § - Aug 04, 2003 7:44:31 am PDT #4515 of 10000
Well not canonically, no, but this is transformative fiction.
I did some more reading, and you're right.
Can you ask your guy if his system is tuned in such a way this would be more efficient for it?