Closed Bug 586988 Opened 12 years ago Closed 10 years ago

Too many HTTPS connections slows down greatly opening sites

Categories

(Core :: Security: PSM, defect)

1.9.1 Branch
defect
Not set
critical

Tracking

()

VERIFIED WORKSFORME

People

(Reporter: Virtual, Unassigned)

Details

(Keywords: nightly-community, perf, regression)

Attachments

(1 file)

User-Agent:       Mozilla/5.0 (Windows NT 5.1; rv:2.0b4pre) Gecko/20100813 Minefield/4.0b4pre
Build Identifier: Mozilla/5.0 (Windows NT 5.1; rv:2.0b4pre) Gecko/20100813 Minefield/4.0b4pre

 

Reproducible: Always

Steps to Reproduce:
1. Import attached bookmarks.html to Firefox
2. Open for first time all 39 tabs (Software folder) in one go for permanently saving "broken" https certificates
3. Remove all offline storage and all history (cache, etc...) to be on fresh uncached browser
4. Restart browser and redo #3 to be sure
5. Open for second time all 39 tabs
Actual Results:  
Tabs are loaded very very very slow...
Some https tabs are loaded blankly (all page is white), some pages are loaded into infinity and some loaded not fully

Expected Results:  
Normal speed with opening HTTPS tabs like in HTTP

Problem occurs trunk builds and stable 3.6.8
Setting x2 more aviadiable connections in Fx options (about:config) didnt fix this issue, so it must be some core bug...

Works fine with Opera
Component: General → Security: PSM
Product: Firefox → Core
QA Contact: general → psm
blocking2.0: ? → -
I can confirm, that Step 5 takes longer than Step 2 and the Symptoms of the actual Behavior.
Did you test against 3.5, 3.0, 2.0 if this has been better in the Past at all?
4.0b6pre - affected greatly
3.6.8 - affected greatly, same like Fx4

3.5.11 - affected partially, because loads sites faster than 3.6&4 and didn't "thinking into infinity"

3.0.19 - looks the best, faster than 3.5.11 (or I'm just imagining things ;p), but still not that fast like other browsers

2.0.0.20 - Can't test due to some bug with self-signed certificates, marked it as remembered, but still Fx asks me about it... ;p
1.5.0.12 - didn't test, probably same like Fx2
I was wrong about 3.5.11, it works the same like version 3.6.8 & 4.0b6pre unfortunately...
So renominating this as blocker for 4.0, because operating with many HTTPS isn't possible with Firefox 4, 3.6 & 3.5.
And changing importance to critical, because this can in some way data loss in HTTPS communication.
Severity: major → critical
blocking2.0: - → ?
We should fix this, but it's not a blocker.
blocking2.0: ? → -
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: perf
What's the status of fixing this bug ? Any plans ? Pipelining coming... at first pipelining had a bug issues with connections. Adding now this bug, it will be a overkill.
I try to reproduce it and can't anymore, so closing it and marking this bug as WORKSFORME.
If anyone still can reproduce it, please post your results, thanks.

Using:
Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:14.0) Gecko/20120330 Firefox/14.0a1
Status: NEW → RESOLVED
Closed: 10 years ago
Keywords: perf, regression
Resolution: --- → WORKSFORME
Virtual_ManPL, thanks for letting us know you can't reproduce it. Let's let somebody else verify this.

If this has been fixed, it may be because of bug 674147. In the patch for this bug, I made it possible for Gecko to do multiple SSL handshakes concurrently. If you can reproduce this problem in Firefox 10, but not in Firefox 11 or later, that is probably why.

Otherwise, this may have been fixed by Patrick's connection handling fixes.

Or, perhaps it is still an issue.
Status: VERIFIED → RESOLVED
Closed: 10 years ago10 years ago
Whiteboard: perf, regression
Half a year passed. I don't see any more issues.
So marking this as VERIFIED FIXED.

P.S.
I can also add that enabling pipelining boost greatly opening many sites in one go.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.