Uploading 100mb to Google Drive takes 4x longer than Chrome
Categories
(Web Compatibility :: Site Reports, defect, P2)
Tracking
(Webcompat Priority:P3)
Webcompat Priority | P3 |
People
(Reporter: jrmuizel, Unassigned)
References
(Depends on 1 open bug, Blocks 1 open bug, )
Details
(Keywords: webcompat:platform-bug, webcompat:site-report, Whiteboard: [necko-triaged][webcompat:sightline])
User Story
platform:windows,mac,linux,android impact:performance configuration:general affects:all branch:release diagnosis-team:networking
STR:
dd if=/dev/urandom of=random.bin bs=1M count=100
- Open https://drive.google.com/drive/u/0/home
- Open network inspector to get timings
- New -> File upload
- Upload random.bin
- Observe the timings of the PUT request to a url like
https://clients6.google.com/upload/drive/v2internal/files
In Firefox I see 43-44s
In Chrome I see 8-11s
Reporter | ||
Updated•1 month ago
|
Reporter | ||
Updated•1 month ago
|
Updated•1 month ago
|
Comment 1•28 days ago
|
||
This bug was moved into the Performance component.
:jrmuizel, could you make sure the following information is on this bug?
- For slowness or high CPU usage, capture a profile with http://profiler.firefox.com/, upload it and share the link here.
- For memory usage issues, capture a memory dump from
about:memory
and attach it to this bug. - Troubleshooting information: Go to
about:support
, click "Copy raw data to clipboard", paste it into a file, save it, and attach the file here.
If the requested information is already in the bug, please confirm it is recent.
Thank you.
Updated•28 days ago
|
Comment 2•24 days ago
|
||
Hi Jeff,
We're aware of some issues with upload speed to Google Drive. I assume in your case the upload is using HTTP/3, right?
Updated•24 days ago
|
Reporter | ||
Comment 3•24 days ago
|
||
(In reply to Valentin Gosu [:valentin] (he/him) {{ PTO 21 Dec - 06 Jan }} from comment #2)
We're aware of some issues with upload speed to Google Drive. I assume in your case the upload is using HTTP/3, right?
What's the best way to determine whether it's using HTTP/3?
Comment 4•24 days ago
|
||
I think it should be visible in devtools, or since bug 1938620 it should also be present in the profiler.
In any case, our leading theory right now is that this is related to our congestion control algorithm that we use for QUIC.
Reporter | ||
Comment 5•24 days ago
|
||
Yes. This seems to be with HTTP/3
Comment 7•16 days ago
|
||
This should have stayed in Web Compatibility
Updated•16 days ago
|
Updated•16 days ago
|
Updated•13 days ago
|
Comment 8•9 days ago
|
||
(In reply to Jeff Muizelaar [:jrmuizel] from comment #6)
What's the plan for fixing it?
We're still investigating it. Probably related to our congestion control implementation in QUIC. Work ongoing in bug 1852924.
Description
•