Hi - I'm running Tixati 2.56, downloaded today. I'm only getting 1000KBPS download speeds, on a system which, it seems to me, should be capable of much more.
Here's what I know:
* I have my incoming bandwidth limit turned off on Tixati.
* Processor: an I3 built in 2012, running at 37% of capacity (according to Windows Task Manager)
* RAM: 8GB, Task Manager says memory use is at 55%.
* Ethernet speed, per Task Manager: 7.7Mbps (appears to be bits? rather than bytes?)
* Connection to router: Cat5 cable
* Modem capacity 450Mbps
* Speedtest.net result 60-80MBPS on a Comcast connection with a nominal max of 200MBPS.
Is this 1000KBPS speed a Tixati limit (is an upgrade or premium version available?), or do I need to be looking elsewhere for a culprit? I'm pretty sure that there's more slack in the connection than needed to support a much higher rate. (like, 60+Mbps???)
I'm not asking someone to break their weekend and educate me, but a link to possible causes for download speed reduction would be a nice-to-have.
--Phil S.,
by
Pete on 2018/01/18 08:18:28 PM
60 Mbps is 7.5 MBps, so I think your task manager shows exactly the same throughput as the speedtest. Tixati uses kB/s for speed limits, you should be able to get about 6000 kB/s. Try setting that as incoming limit and set outgoing limit to 3/4 of your maximum upload bandwidth. Use speedtest to measure upload bandwidth. I think your unlimited outgoing data is choking your download.
For example I've got 50 Mbps download and 10 Mbps upload bandwidth. I set incoming limit to 5000 kB/s and outgoing limit to 800 kB/s for downloading. For seeding I set both limits to 900 kB/s. I know these settings work well, I browse web normally while Tixati is downloading or seeding at full speed.
by Guest on 2018/01/22 09:52:12 PM
Pete,
I just figured it out. The program panel includes an "auto limit" button. Said button was lit. On clicking it, hey, presto, the button goes off, and SHAZAM - Download rises to the 5000KB/s line (my value in "Limit Incoming KB/s"). It looks like Auto Limit might have been defaulted to enabled, which I find irritating, but I'm not sure -- I might have hit it while I was trying to make things work at install time.
--Thanks,
Phil
