Open Bug 1597837 Opened 5 years ago Updated 2 years ago

Suggestion: Increase priority of "fetch" requests, to prevent pauses when playing music or Spotify Web Player

Categories

(Core :: DOM: Events, enhancement)

72 Branch
enhancement

Tracking

()

UNCONFIRMED

People

(Reporter: wtds.trabalho, Unassigned)

References

Details

Attachments

(1 file)

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

Steps to reproduce:

  • Developer
  • Many tabs, searching many things
  • Audios pauses and breaks frequently
  • I see apparent slowdown on Spotify Web Player "FETCH" requests

Suggestions:

  • Please prioritize fetch request and other media requests over others networks requests.
  • Prioritize Spotify and media player tabs than others tabs.

Request headers:

GET /audio/0b09d174326fd16289707ef4349e9a839d7dda28?1574212001_k7G2S2l5rWvKukvQ9qh9-aA15tRgyEtwSuzBPTI2Ef0= HTTP/1.1
Host: audio-fa.scdn.co
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/search/Classic%20Pop%20Rock
Range: bytes=2011120-2343557
Origin: https://open.spotify.com
DNT: 1
Connection: keep-alive
Pragma: no-cache
Cache-Control: no-cache

and Reponse Headers:

HTTP/1.1 206 Partial Content
Last-Modified: Fri, 05 Aug 2016 11:44:22 GMT
ETag: "3e09297a5e2b7db04e933efcf6b176dd"
Content-Type: application/octet-stream
Age: 20006474
Content-Range: bytes 2011120-2343557/9840246
Content-Length: 332438
Accept-Ranges: bytes, bytes
Date: Wed, 20 Nov 2019 00:08:11 GMT
Connection: keep-alive
X-Served-By: cache-ord1733-ORD, cache-gru17133-GRU
X-Cache: HIT, HIT
X-Cache-Hits: 0, 0
Access-Control-Allow-Origin: *
Cache-Control: max-age=315360000, no-transform

Actual results:

Slow audio play with many pauses.
Slow fetch requests responses.

Expected results:

Improve Spotify audio play priority over other non multimedia tabs.

Thanks!

I cannot properly reproduce this issue on my systems. Setting component as (Core) DOM: Events.
NI me if further testing is needed.

@reporter: Did you reproduce this issue in Nightly v72.0a1 on a Linux OS?

Component: Untriaged → DOM: Events
Flags: needinfo?(wtds.trabalho)
Product: Firefox → Core
Attached file My-support-info
Hi Bode,

Yes, I can. Try to test in slow machine or PC with limited computational resources. 




Thanks!

Hi,

I think the order off resources load is more visible in slow PCs.
But I'm still suggest the optimization for all scenarios.

Thanks!

Flags: needinfo?(wtds.trabalho) → needinfo?(daniel.bodea)

I have reattempted to confirm your issue on Ubuntu 18 by forcing CPU to 100% and memory to almost 100% on a pretty slow machine, but the Spotify sang nicely.
We should leave this enhancement to be investigated by a developer. Thank you.

Flags: needinfo?(daniel.bodea)

Maybe I'm just imaging things, but "pulling" spotify tab to a separate window (thus making its performance not depend on my thousand-tabs strip usual overhead) seemed to do the trick for me.

This may also cause bug 1586518.

See Also: → 1707762
Severity: normal → S3
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: