Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

High CPU usage in RarityMap.recalculate and BitField.get #810

Open
feross opened this issue May 20, 2016 · 3 comments
Open

High CPU usage in RarityMap.recalculate and BitField.get #810

feross opened this issue May 20, 2016 · 3 comments
Milestone

Comments

@feross
Copy link
Member

@feross feross commented May 20, 2016

screen shot 2016-05-19 at 20 54 22

This happened when adding two Ubuntu ISO files in WebTorrent Desktop.

@FinnFrotscher

This comment has been minimized.

Copy link

@FinnFrotscher FinnFrotscher commented May 29, 2016

Yes. +1
When I run webtorrent inside electron, it takes about 10 minutes until my mac is completely overwhelmed with a cpu load of 100% and it is only after I kill the electron and chrome processes that it drops down to normal (5%). Running the same electron without webtorrent the overload doesnt happen.

screenshot

@feross

This comment has been minimized.

Copy link
Member Author

@feross feross commented Jun 6, 2016

@FinnFrotscher The issue you're describing sounds like #551 which is fixed by updating to the latest version of Electron. This issue was fixed in Chrome 51 and Electron 1.2.0. Make sure you're on that version, for both your local and global installation of Electron.

@dcposch dcposch added this to the v1 milestone Sep 20, 2016
@feross feross added the accepted label May 3, 2018
@feross

This comment has been minimized.

Copy link
Member Author

@feross feross commented May 4, 2018

I think this is causing download speeds to jump. My guess is that we're downloading too fast for WebTorrent to handle processing the data (we're doing something inefficient somewhere). This spikes the CPU to 100% during which time we're blocked and not acknowledging data from peers, so they lower their speeds.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.