Open
Bug 1304629
Opened 9 years ago
Updated 3 years ago
Decide the prioritization in IsSpecialProtocol for performance
Categories
(Core :: Networking, defect, P3)
Core
Networking
Tracking
()
NEW
People
(Reporter: CuveeHsu, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: perf, Whiteboard: [necko-backlog])
IsSpecialProtocol isn't expensive but it's easy to prioritize that which protocol we want it faster. It takes 0.1 micro sec for each comparison |protocol.LowerCaseEqualsLiteral(PROTOCOL_NAME)|.
|
Reporter | |
Comment 1•9 years ago
|
||
Originally I guess HTTPS should deserve more respect than HTTP, and get more user.
However, HTTPS only have 3X% according [1]
[1] http://httparchive.org/trends.php#perHttps
|
||
Comment 2•9 years ago
|
||
if that's worth optimizing build a state machine and walk the string (i.e. that thing should be 6 char compares at most instead of a linear string walk followed by up to 7 string compares and a string copy!
the name isSpecialProtocol should also be changed to isSpecialScheme for accuracy.
|
|
Reporter | |
Updated•9 years ago
|
Whiteboard: [necko-active] → [necko-backlog]
|
||
Comment 3•8 years ago
|
||
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: -- → P1
|
|
||
Comment 4•8 years ago
|
||
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: P1 → P3
|
|
Reporter | |
Updated•8 years ago
|
Assignee: juhsu → nobody
|
||
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•