Sites sometimes can take a long time to load because of Queueing in Brave.

ipfs / ipfs-companion

Browser extension that simplifies access to IPFS resources on the web

https://docs.ipfs.tech/install/ipfs-companion/

Creative Commons Zero v1.0 Universal

2.05k stars 325 forks source link

Sites sometimes can take a long time to load because of Queueing in Brave. #1025

Open GaponkaGapon opened 3 years ago

GaponkaGapon commented 3 years ago

I'm using Brave browser currently. I'm not sure, if this is issue with Brave or IPFS, but I will write here about it. Brave support IPFS out of the box. But there is also an option to install IPFS companion extension right in Brave settings, which I did. I should notice, that desktop IPFS node is not installed. When using Brave, companion works in the background somehow even when you're not using any IPFS resources at the moment, which is ok. But sometimes, when you trying to load regular (non IPFS) site it takes several seconds more (like 8 seconds) than expected. When companion is off, it doesn't happen. I have looked at developers tools. It's seems to me, that problem lies in Queueing phase which described here: https://developer.chrome.com/docs/devtools/network/reference/#timing-explanation

As I said, sometimes it takes several seconds. Screenshot 2021-09-13 151832

lidel commented 3 years ago

@GaponkaGapon do you mind helping us with reproducing this?

what is your operating system?
what Brave version are you running?
do you have any other extension running?
are you able to reproduce it on any page, or only specific ones? (if so, mind linking example?)
does this occur every time, or only during the first load?

GaponkaGapon commented 3 years ago

@lidel

Windows 10
Latest. Just updated. 1.29.80. Still reproducible.
Turned off all other extensions and reloaded Brave. Still reproducible.
I think it can be reproducible on any site with some probability.
I did not managed to reproduce it several times in short period of time on same site. After first load, fast or slow, everything is ok. But it's relatively easy to reproduce, when you trying different sites.

Also I tweaked extension settings before, so I would not be directed on IPFS version of sites or gateways automatically. But I don't think it's relevant.

lidel commented 2 years ago

I was not able to reproduce.

It sounds like what you describe is just your IPFS node looking for and fetching website data for the first time using p2p transport. After data is cached in your local datastore, then it loads fast (that is why subsequent page loads are not slowed down).

Lmk if this makes sense, or you have a reliable way for reproducing this.

GaponkaGapon commented 2 years ago

@lidel, I'm talking about regular non-IPFS sites. As far as I know, Brave's own IPFS node doesn't work in the background, when you're not on IPFS resource, and when you're not using companion. With companion is on problem appears. Maybe those are troubles with my ISP. But, as far as I understand, Queuing step is not about that. It's about browsers internal work. Sorry, but, I think, I can't tell more than that.

github-actions[bot] commented 2 years ago

Oops, seems like we needed more information for this issue, please comment with more details or this issue will be closed in 30 days.

github-actions[bot] commented 2 years ago

This issue was closed because it is missing author input.

lidel commented 2 years ago

We should revisit this after MV3 work lands (#666) – i suspect the forced switch to declarative API we will experience in MV3 might improve the situation.

GaponkaGapon commented 2 years ago

I'm currently on Linux for several months already (Pop!_OS). Using companion with no visible problems. I just cleared most of browsing data and checked many sites. I managed to reproduce problem with queuing only twice. And I tried a lot. It was worse before.