Let me disclaimer this by saying that this is actually being done in ASP but I believe it to be more of a mySQL thing and PHP guys usually know more about mySQL than us ASP M$ lovers. And, knowing about how little I look at PHP sub-forums, you all might not ever see this if I dropped it into the ASP one.


Okay......this is an oddball situations if I've ever seen one.

I have page1 and page2

The scenario is that page1 SELECTS from about 3 tables. It calls page2 who SELECTS those same 3 tables plus 2 others. Page2 will eventually call back to page1. When page1 is getting the call back from page2, it does an update before SELECTing those 3 tables again. The UPDATE is done against one of those 3 tables. When page1 calls page2 the second time (or any time after that) page2 loads very very very slowly.

Now, I can call page2 over and over and over all by itself with no problem. In fact, I can call page1 (so that it doesn't execute the Update) and then call page2, then back to page1 (still without the Update) and back to page2 and still have no problem.

I can go into page1, comment out the Update command, go through the whole sequence and there will be no slow down whatsoever.

Why the HECK is that Update slowing down a SELECT on the table it's UPDATE 2 calls away?!?!?!?!

Oh, one other thing......

If I close out the browser after the second call to page1 (where after page2 gets slow), open a new one and call page2, I can actually get page2 up quicker that way.

So, apparently, something having to do with my browser session is helping slow down this page.

Also, I am closing out my database connection at the bottom of every page.

Anyone who can figure this out for me would be my hero