28012 - Urls loading on the Isolate lan are taking to long

Status: VERIFIED FIXED

(Core :: Networking, defect, P3)

Description

[Paul Wyskoczka]

Overview Description: 
When running our performance tests on the Isolated Lan, we are noticing that 
it takes a long time for urls to load in the browser.  In Communicator 4.72 
loading a page will take on the order of 2-3 seconds where Seamonkey is taking 
16-17 seconds.  Seamonkey is slower but not that slow.  We are unable to obtain 
performance data that is reliable.
Steps to Reproduce:
1)Setup the Isolated lan configuration
2)Run the perl performance script or load pages manually
3)Check the results

Actual Results: 
Page loads are slow

Expected Results: 

                    
Build Date & Platform Bug Found: 
Windows 95.  Builds are not an issue here.
                    
Additional Builds and Platforms Tested On: 
None
                    
Additional Information: 
None

Comment 1

[Warren Harris]

I'll take this one.

Comment 2

[leger]

Putting on the PDT+ radar for dogfood.

Comment 3

[Paul Wyskoczka]

Jud looked at this last time we had a problem in this area.  Adding valeski to 
the cc list.

Comment 4

[leger]

will give til 03/03 if needed.

Comment 5

[Warren Harris]

I added the ability to set the environment variable DNS_TIMING before doing a 
run which will enable the file dns-timing.txt to be dumped out. From this I'm 
hoping that we can see whether dns is the culprit or not. I've asked leger and 
paw to give it a try.

Comment 6

[Warren Harris]

We got this dns timing stuff going just in time to realize that the recent 
changes to remove MOZ_PERF have brought win95 back up to acceptable levels of 
performance for the beta. Consequently I'm closing this.

Comment 7

[Warren Harris]

P.S. Enclosing a log of one of Paul's recent runs, showing that dns lookup time 
is not significant.

Comment 8

[Warren Harris]

Attachment: dns timing for isolated lan

Comment 9

[Paul Wyskoczka]

Tom, I'm going to verify this since I was working with Warren on this bug eventhough you are the QA contact.