TorrServe MatriX

📺 TorreServe - to convert a torrent file into an http link for online viewing in a player or for downloading in a browser.

❗Settings for different devices:

⚪ A powerful device for a server, no power limitations: ▫️Cache size: 160 ▫️Connections limit (torrent connections): 25 🔸Torrent size is unlimited

⚪ TV\weak set-top box (2GB RAM): ▫️Cache size: 64 ▫️Connections limit: 20 ▫️Download rate limit: 12000 🔸Torrents no more than 50-60GB

⚪ Router (256MB RAM): ▫️Cache size: 32 ▫️Connections limit: 10 ▫️Download rate limit: 2000 🔸Torrents no more than 7-8GB

---

⚪ In all cases: ▫️Preload buffer (Fill cache before start): Yes ▫️Reader readahead (Cache preload): 90 ▫️Torrent disconnect timeout: 20 ▫️Disable UTP: Yes ▫️Upload rate limit: 8000 ▫️Dht connection limit: 500 🔸Don't change anything else. 🔸If the player is Vimu, then put 50 in the buffer instead of Auto.

If the question arises - why such a small cache, I’ll explain:

The cache size is not equal to the size of the RAM used. She will eat more. 128MB is 1280Mbps A 100 gig avatar has a total average bitrate of 80 Mbit/s (the video stream and all audio tracks are inseparable from the file you are downloading) 1024\80 = ~16 seconds That is, a 160MB cache allows one of the most complex torrents to be stored in memory for as much as 16 seconds in advance. And films of 50-60GB take almost half a minute. You don't need more. You don't need to use 200-400-1000MB in cache. In addition, at values ​​above 200MB of cache, the server (no matter what version) may inexplicably become slow.

Last but not least, don’t run torrents with less than 15-20 seeds!

Source code available on GitHub: https://github.com/YouROK/TorrServe Full list of changes: https://github.com/YouROK/TorrServe/releases