Just curious, but which version of PHP are you using, the ISAPI or CGI.
I've tried the isapi version before and had problems like this.  PHP
would crash and leave orphaned instances of php.  If your using the
isapi version try the cgi and see if it works for you.





-----Original Message-----
From: Peter Westergaard [mailto:[EMAIL PROTECTED]] 
Sent: Tuesday, January 08, 2002 6:39 PM
To: [EMAIL PROTECTED]
Subject: Re: Pulling a long list of data stalls PHP


Miles, you wrote:
 >Is your table indexed on the field your query is based on? That will
>greatly speed up the query.  >  >Miles Thompson

I'm afraid in my case, the query needs to be pretty much a complete
table dump.

Even if I filter a subset the data, my relational DB experience (not
deep, admittedly, and only with enterprise products like Oracle and ...
ugh...
MSSql) tells me that indices on tables less than a few thousand entires
cost more in upkeep than they gain in response.  And this is only about 
300-400 rows... and more to the point, this happens when I pull more
than 
30 of them or so!  I feel that something MUST be wrong!

But all of that aside, the problem isn't just that it takes a "long 
time"... the
problem seems to be that it literally *crashes* the instance of PHP!
(The webpage never finishes loading, and the CPU meter drops back down
to idle levels, and if I cancel the webpage, I leave an orphaned
instance of PHP.exe running, which I cannot kill even from my Win2000
Task Manager).

I mean, I'm a newbie and I'll admit that, but that just Don't seem
Right.

Does ANYONE have any idea what might be happening and how I can fix it?
Please? :)

-P



-- 
PHP Database Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to