Buffistas

Riley: Oh, yeah. Sorry 'bout last time. Heard I missed out on some fun. Xander: Oh yeah, fun was had. Also frolic, merriment and near-death hijinks.

'Never Leave Me'

Buffistas Building a Better Board

Closed Threads

Do you have problems, concerns or recommendations about the technical side of the Phoenix? Air them here. Compliments also welcome.

To-do list

First Previous Next Last Recent

Cindy - Aug 03, 2003 2:54:17 pm PDT #4502 of 10000

Nobody

Just got this at the top of the home page, now:

August 3, 2003, 4:53 pm : ERROR [2] mysql_close(): no MySQL-Link resource supplied line 81 of file /home/bufforg/public_html/classes/giles.php

§ ita § - Aug 03, 2003 3:35:29 pm PDT #4503 of 10000

Well not canonically, no, but this is transformative fiction.

Okay. I'm going to upload some new changes, that have been somewhat tested. Hopefully there will be no mean messages, but bear with me.

§ ita § - Aug 03, 2003 3:41:05 pm PDT #4504 of 10000

Well not canonically, no, but this is transformative fiction.

This isn't slutting, this is further testing.

Cindy - Aug 03, 2003 5:03:03 pm PDT #4505 of 10000

Nobody

Pshaw.

I never got the messages again, for what it's worth. Even before your post about making more changes.

Jon B. - Aug 03, 2003 6:05:01 pm PDT #4506 of 10000

A turkey in every toilet -- only in America!

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.

§ 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.

First Previous Next Last Recent