PyroScope Project comments

Results 60 comments of


                                            PyroScope Project

Support concurrent hash checking

concurrent hashing = disk trashing = not reasonable.

Support concurrent hash checking

BTW, one single item can live on several file systems (and current code acknowledges that).

rTorrent reading 4x more data than sending

It could also be kernel read-ahead. Someone with time + interest should look into that with sysdig.

rtorrent aborts with message about "initial seeding"

Including the hash would greatly improve diagnostics for this type of message.

Random crashes - 'Non-existent physical address.'

You MIGHT get away with fuse when used read-only regarding the mmap access. So set your download dir to an ext4 filesystem, then move on completion to the fuse one....

Increased threading for peer connections

The sensible architecture for things like that is threads per work unit, not threads per (idle) resource. So have the main thread dispatch *actual* IO and processing the data to...

[Feature Request] enable torrent renaming via d.set_name=

different libtorrent, so not really relevant

[Feature Request] enable torrent renaming via d.set_name=

@drzraf no. read the [BitTorrentSpecification](https://wiki.theory.org/BitTorrentSpecification) if you want to know why.

segmentation fault; libphtread / libcurl with http.max_open >= 300

your configuration tries to use >1024 handles, so fix your machine config to be able to use more.

segmentation fault; libphtread / libcurl with http.max_open >= 300

Do not configure more than ~950 handles in a vanilla Linux setup, and also use a non-broken curl. Not considering those two is 99.9% causes of problems with HTTP requests.