PHP Objects falling into the void

Anon

OK, here's a problem that I've noticed with an OOD codebase that uses a MySQL wrapper for database abstraction....

It seems that when I try to insert >600 rows of Data into the MySQL database, the PHP process dies and sends some malformed header
which then becomes a DNS error page in IE about a minute later.

I've tried all kinds of stuff to get the processes to run faster, such as locking tables, using LOAD DATA INFILE rather than inserts etc.

Now the Kicker here is that I can run the same LOAD DATA INFILE statement in mysqladmin and get all 1065 rows of data inserted w/o a hitch.

I'm thinking that this may be a serious issue with Objects and external resources in PHP. I'll admit I have a funky setup with over 20 global objects floating around, but this is the first I've seen a performance hit. And it's pretty bad.

Might it be some memory overhead?
I tried using mysql_free_result...but I think the suction started with the actual mysql_query(). Maybe there is some magic command that I could use to make the software send off the query and then forget about it or better yet, allocate higher overhead clearance for the objects.

Anyone have any pointers as to how the
MySQL interaction could be tamed?

Anon

make sure your headers are all right... make sure the script can get done before the max execution time of php... make sure none of the input is getting 'magic quoted' /' //''////'/ '"///"" that can be a mess.

Anon

I have an object to handle variable input since I don't like magic_quotes, I use add_c_slashes as that affords me greater control over what get's slashed and what doesn't.

But, the data is not comming via input it's comming in through my code and nothing is slashed.

The headers are fine and the script works great if the database connection isn't made.

I should note that large SELECT statements against a 4meg table with over 156K rows execs very quickly with my MySQL wrapper object on the same database, it's just doing the inserts that seems to cause the object to get lost...
I'm almost thinking about removing the key indexing during the insert since that will allow the MySQL server to not have to buffer the index keys.

...but your point about headers made me think about something just now.

I am using Output Buffering, maybe I'll turn that off and test it again. But it would be a shame to lose that since I did like the auto-gzipping that came with it.
But OB does affect the headers that are sent.

Anon

obviously this is going to end up being some obscure incompatibilty in one of the 20 objects you are using, so no one here can really help you. if your setup is right, then the problem is just with how the objects interact. sorry.

Anon

No, actually, thank you.

That bit about the headers put me on the right path, appearantly, OB was causing the headers to be malformed since they were never completed due to the script collapsing,
I just took that out in the super class and all looks good now.

And I'd much rather deal with 20 objects than a bunch of include files buried inside a bunch of embedded scripts... man that would make me want to make my vocation in the fast food industry for sanities sake 🙂

But this one looks like a case of a small bug with a relatively new feature. OB with gzipping appearantly doesn't have a fail-safe in the event that a script can't complete the header appropriately due to problems, so it just lags and the entire page falls into a sink-hole preventing you from even knowing where the problem is.

But, again... thanks for the added insight, saved me a few hours of looking in the wrong direction.