Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upextremely high cpu usage when adding a torrent #122
Comments
This comment has been minimized.
This comment has been minimized.
|
I've noticed this as well. I suspect it is caused by the code for verifying Of course, this is only a guess. On Monday, June 9, 2014, Viktor Stanchev notifications@github.com wrote:
Feross | blog http://feross.org/ | webtorrent http://webtorrent.io/ | |
This comment has been minimized.
This comment has been minimized.
|
I confirmed that it's caused by https://github.com/feross/bittorrent-client/blob/master/lib/torrent.js#L560 However, setting {verify: false} in the BitTorrentClient constructor doesn't seem to bypass this verification. |
This comment has been minimized.
This comment has been minimized.
|
Hmm, the verification code for non fs-storage should run in no time since all reads are shortcuts, but clearly there's an issue with the implementation. |
This comment has been minimized.
This comment has been minimized.
|
Closing out old issues. Feel free to comment or open a new issue if this still affects you. |
Tuesday Jun 10, 2014 at 05:49 GMT
Originally opened as https://github.com/feross/bittorrent-client/issues/26
Whenever I add a torrent (from a content hash) I get extremely high cpu usage for a while until it stops and streaming starts. It seems to have something to do with sha1 hashes and verifying pieces. This didn't happen in version 0.1.1. Has anyone else experienced this? If not, I'll try to get more details.