Database results in Netscape

Different from IE?

[Big_Perm]

I have an ASP page that displays about 5,000 records perfectly in Internet Explorer in about 8 seconds, but when I open the same page in Netscape, it loads to 93% and then takes about 4 minutes to load. Any ideas?

[Brett_Tabke]

My first thought, Microsoft Server? Has to due with the headers msiis is expecting and those that netscape sends out (ms is wrong of course). (there is a fix running around somewhere for this - sorry, not the iis guy).

Or, a particular js construct that is causing nn to fry for a long time?

[Big_Perm]

It is Microsoft IIS and i'm using VBScripting and no js. The database is Access '97. Another page that is essentially identical to the slow loading one returns 700 records and loads in about .5 seconds. The only difference is the SQL, and both query the same table.

[jatar_k]

That sounds a bit suspect. What version of netscape is it?

Netscape is picky, it could be one small tag left out somewhere. Am I right in understanding that the slow page shows 5000 records and the fast one shows 700? The difference could be something that is exponential in its impact. Such as too many tables or nested tables. Sounds funny, I'm not totally sure.

There must be more differences in the pages than just the SQL.

[Big_Perm]

The only difference besides the SQL is that the page that returns 5000 records displays 4 fields, and the 700 records displays 3 fields.

NN 4.76 --> 5000 records --> 1 min 20 sec <-- Browser stops responding, eventually displays records
NN 4.76 --> 700 records --> 4 sec

IE 5.0 --> 5000 records --> 10 sec
IE 5.0 --> 700 records --> 4 sec

[jatar_k]

It would seem that your queries aren't the problem if you can get it to return so quickly for 3 out of the 4 scenarios. I would look into the fundamental differences in rendering between IE and Netscape. IE renders on the fly and Netscape 4.76 renders when the page is loaded, nested tables cause more slow downs with netscape than IE. One switched tag can cause netscape not to render but IE will fake it.

I wonder if it would work properly in netscape 6 given that it has more IE like behaviours? I really think from the little I know about this situation that I would look to the HTML first and see if you can speed it up that way. I have had the exact same thing happen with SQL functions that populate and display arrays using tables and often the solution was to have the diplaying query spit out rows instead of full tables. It can increase the rendering time exponentially.

[joshie76]

This is a common problem when using Netscape 4 and browsing your local web-service (i.e. localhost/ or <computername>/)

It is due to a bug in Netscape 4 which hogs priority in windows and leaves little processing power for your IIS to work through the ASP. You can manually adjust NN4's priority using task manager or, the way I get around it, is to minimise NN4 for a couple of seconds after a submit.

Obviously, if you're browsing a server on another machine then netscape should be fine and this isn't your problem.

Josh

[Big_Perm]

I am browsing a server on another machine. I've tried putting the results into an array and displaying the contents of the array. I've also tried using disconnected recordset. I checked the html and cleaned it up as much as i could. It seems like the size of the database results is the problem, I have no idea.

[jatar_k]

it almost sounds like a necessary evil.

I do the same type fo thing using php and i run 4 nested loops working on about 1000 rows of data doing calculations in each loop for each record and I max out at about 30 sec. With the nested loops it reads each row 4-16 times so I know you can speed it up (I also only use netscape 4.74).

I just don't quite know exactly how off the top of my head without seeing what we are talking about. It may just be that one in 4 people have it return a little slower and you should go with a loading image or message.