SOLVED! Now I am running with:
i2np.ntcp.maxConnections=3333
i2np.udp.maxConnections=111
and open trackers off.
More peers connected, 20-30% better throughput and significantly less CPU at the same time.
Search found 45 matches
- 26 Feb 2018 19:49
- Forum: I2PSnark
- Topic: 0.9.33 Snark traffic "vanishes"
- Replies: 8
- Views: 39937
- 26 Feb 2018 19:32
- Forum: Router
- Topic: 0.9.33 rate limits
- Replies: 5
- Views: 22376
Re: 0.9.33 rate limits
Thanks, found it in the "i2p hidden services" section by clicing on "i2p webserver". So it will not affect anything else.
- 26 Feb 2018 06:18
- Forum: I2PSnark
- Topic: 0.9.33 Snark traffic "vanishes"
- Replies: 8
- Views: 39937
Re: 0.9.33 Snark traffic "vanishes"
I have watched this quite some time now. Traffic does not exactly vanish, but with 0.9.33 most of the time only part of the leechers do actually connect. So less traffic per torrent and Snark hands out the same pieces again and again because not all bitfields are known with the effects described abo...
- 26 Feb 2018 04:59
- Forum: Router
- Topic: 0.9.33 rate limits
- Replies: 5
- Views: 22376
0.9.33 rate limits
The 0.9.33 release notes mention rate limits being introduced. I did see nothing in the hidden service manager. Any hint to some documentation would be helpful to decide whether I have to adapt something.
- 19 Feb 2018 09:45
- Forum: I2PSnark
- Topic: 0.9.33 Snark traffic "vanishes"
- Replies: 8
- Views: 39937
0.9.33 Snark traffic "vanishes"
I am putting it here because new topics are disabled in "I2PSnark". Snark does not work in 0.9.33 as in previous versions. Since I have only metrics, no hard facts I am not yet opening a Trac ticket. I am always seeding several large torrents with 5 - 15 leechers and have noticed that sinc...