Closed Bug 1342743 Opened 9 years ago Closed 2 years ago

Cannot saturate downloads on Gigabit connections

Categories

(Core :: Networking: HTTP, defect, P3)

51 Branch
x86_64
Linux
defect

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: thebrian2008, Unassigned)

References

Details

(Whiteboard: [necko-next])

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:51.0) Gecko/20100101 Firefox/51.0 Build ID: 20170126200443 Steps to reproduce: During speed tests, downloading, or when using Firefox with heavy traffic or duing task the use multiple streams. Actual results: Firefox cannot saturate or take advantage or Gigabit speeds. It does appear to get over 700 Mb/s overall saturation. Expected results: Should of been able to get full saturation. Other browsers tested such as Chromium are able to.
OS: Unspecified → Linux
Hardware: Unspecified → x86_64
Component: Untriaged → Networking: HTTP
Product: Firefox → Core
The report contains to few information. I just tested downloading data on a gigabit LAN and Firefox was able to utilize full network bandwidth. Provide detailed information about the test you did.
Flags: needinfo?(thebrian2008)
(In reply to Michal Novotny (:michal) from comment #1) > The report contains to few information. I just tested downloading data on a > gigabit LAN and Firefox was able to utilize full network bandwidth. Provide > detailed information about the test you did. Using a simple speedtest provided by the ISP shows a marginal difference between Firefox and Chromium. https://www.youtube.com/watch?v=yweL7tFemHY The results are the same with HTML5 test. Whether http or https
we've had a couple reports like this (tho I cannot find the dups right now) so its worth digging into. iirc it depends on the context the resource is requested from (or has in the past) so it probably isn't a wire-networking issue (like a window being too small) but is overhead in the machinery of getting the data to the caller.
Whiteboard: [necko-next]
See Also: → 1329486
Flags: needinfo?(thebrian2008)
Priority: -- → P2
Moving to p3 because no activity for at least 1 year(s). See https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage for more information
Priority: P2 → P3
Severity: normal → S3

We have other bugs to track the performance of download/upload, so I'd like to close this one.

Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.