Closed Bug 1598137 Opened 6 years ago Closed 4 years ago

Suggestion: Increase 206 request network priority and importance (Audio playing)

Categories

(Core :: Networking, enhancement, P2)

Product:
Core
Component:
Networking
Version:
72 Branch
Type:
enhancement

Tracking

()

Status:
RESOLVED INCOMPLETE

People

(Reporter: wtds.trabalho, Unassigned)

Details

(Whiteboard: [necko-triaged])

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:72.0) Gecko/20100101 Firefox/72.0

Steps to reproduce:

  • use spotify web player at Firefox
  • disable addons
  • see strange delay in 206 request of Spotify to Akamai

Audio pause many times, because is slow to low the parts of the audios.

Request headers:

GET /audio/9a30926fbd75a774f7e5744dbb6b3a325eda3b37?__token__=exp=1574290181~hmac=8039fffb67ec9fb24503dad0973f2e6d51c28a28a29b795fd5eec28c62169403 HTTP/1.1
Host: audio-ak-spotify-com.akamaized.net
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:72.0) Gecko/20100101 Firefox/72.0
Accept: */*
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate, br
Referer: https://open.spotify.com/browse/featured
Range: bytes=5408038-5740876
Origin: https://open.spotify.com
DNT: 1
Connection: keep-alive
Pragma: no-cache
Cache-Control: no-cache

Response headers:

HTTP/1.1 206 Partial Content
Last-Modified: Sat, 16 Sep 2017 03:25:48 GMT
ETag: "e64a97e42c502137f5999f86e88f22fd"
Content-Type: application/octet-stream
Accept-Ranges: bytes
Content-Range: bytes 5408038-5740876/8659672
Content-Length: 332839
Cache-Control: no-transform, max-age=29814197, max-age=315360000, no-transform
Date: Wed, 20 Nov 2019 21:58:58 GMT
Connection: keep-alive
Access-Control-Max-Age: 86400
Access-Control-Allow-Headers: range, pragma, cache-control
Access-Control-Allow-Methods: GET
Access-Control-Allow-Origin: *
Expires: Sat, 17 Nov 2029 21:58:58 GMT

Actual results:

Prioritize GET of 206 partial audio content over PUT and POST requests.

Expected results:

I want to browser downloading parts of audio before do PUT and POST requests.
And do GET of 206 audio parts before other network actions.
Make audio player more fluid.

Thanks!

Hey Wellington,

Do you have by any chance a slower internet connection?
I don't have any audio pauses during playback and seems to work fine, latest Nightly 72 on Windows 10.

Flags: needinfo?(wtds.trabalho)

Hi Timea...

No, no chances of slow internet:
https://www.speedtest.net/result/8799881847
https://www.speedtest.net/result/8799881847.png

But very slow disk IO, and poor desktop computer(It's my PC in the company, i like to develop listening Spotify)
I know, it's very specific scenario, but you can try slowdown the browser or machine...

Thanks!

Flags: needinfo?(wtds.trabalho) → needinfo?(tbabos)

HI,

I'm the only in the company at this time.. and the PC speed appears to have influence in browser speed and in browser requests...

The same test, after some minutes from the previously post:
https://www.speedtest.net/result/8799889386
https://www.speedtest.net/result/8799889386.png

I suggested the prioritization and other improvements to prioritize audio/videos experience instead other background operations.
Creating a simulations of responsiveness at the browser. Or something like this.

I'm remembering now about HTTP priorization and request prioritization marks... There is support for something like this in Firefox?
If that ways available, Spotify and other can organize the site request priorities and send isntructions to the browser.

Thanks!

Best I can do here is to set it up as an enhancement and see if the devs have any solution at hand or further info on how to improve this.
Thanks for the report!

Component: Untriaged → Networking
Flags: needinfo?(tbabos)
Product: Firefox → Core

This will be a bit more complicated than just prioritization I suspect. I'll look into it more in depth. Hopefully the web player will work the same way in Central Europe. Wellington, can you at least roughly reveal your geolocation? Thanks.

P2 for investigating what is actually happening here.

Priority: -- → P2
Whiteboard: [necko-triaged]

I don't think this is reproducible.
If you still find this happens please let us know and reopen. Thanks!

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