Closed ValdikSS closed 1 year ago
That is really cool input, many thanks!
I will have a look at it in the upcoming weeks to see what if this can be implemented easily. I understand that you did this without using this project but with your own environment? If am wrong and you did already modify this project, a PR would be highly appreciated :smile:
But again, many thanks for the great feedback and I will have a look into it :+1:
I understand that you did this without using this project but with your own environment?
Yes, just a regular Tor and regular aria2.
The command like for aria used was:
aria2c -s 16 -x 16 -j 3 --stream-piece-selector=random --http-proxy='127.0.0.1:9052' --save-session=session.state \
--http-accept-gzip=true -i session.state --save-session-interval=60 --max-tries=0 --retry-wait=5 -l log.txt --log-level=info
I understand that you did this without using this project but with your own environment?
Yes, just a regular Tor and regular aria2.
The command like for aria used was:
aria2c -s 16 -x 16 -j 3 --stream-piece-selector=random --http-proxy='127.0.0.1:9052' --save-session=session.state \ --http-accept-gzip=true -i session.state --save-session-interval=60 --max-tries=0 --retry-wait=5 -l log.txt --log-level=info
V2ray configuration:
Many thanks for that !!!!
With the recent additions by @reece394 this should be fixed.
Might be good to keep this one open due to 1. not being implemented yet as filtering tor nodes offers a significant performance uplift. If I have time at a later date I will try and implement an automated solution to do this if someone else doesn't tackle it first
Hi there. This is not an issue with the project.
I've had to download 950 GB from Tor recently, from a very slow server, for which I used aria2, and found your project in one of aria2's issues as a pingback. Here are some of the caveats your system does not address:
Tor is an anonymous system, that's why it selects entry and intermediate relays using various metrics. However, for downloading purposes we should prefer relay speed and latency, not anonymity.
You can use tor-relay-scanner to filter the relays, I used filtering by the countries closest to mine, for the lowest possible ping.
Tor shares (aggregates), or non-isolates, circuits based on the clients' source IP address, SOCKS port, destination port, etc. In your configuration, it would aggregate the circuits as long as possible, leading to lower overall downloading speed. I ended up configuring v2ray proxy as a balancer, but each connection uses random source localhost IP
(127.0.0.1, 127.0.0.2, 127.0.0.3, ... 127.0.0.50)
, to make Tor believe that each of the connection is a unique client required circuit isolation. This way you don't have to configure that many Tor instances, I had only three, each of which used 30+ unique circuits.Check
SocksPort
Isolate*
options in the man to learn more. Circuits could be checked using control port withGETINFO stream-status
andGETINFO circuit-status
commands.Is it very important to use
--max-tries=0 --retry-wait=5
configuration for aria, otherwise it won't reestablish the connection in case of failure indefinitely. I also used--http-accept-gzip=true
to speed-up uncompressed text files transfer, as well as some other compressible data. However pipelining, which is enabled in your configuration, I believe slows things down a bit, as the additional TCP connection is almost always more preferable than additional transfer inside existing connection.