Hey, could you check is it possible or not?
There are many servers on old Xeons with low CPU frequency and high core count, so it becomes a bottleneck with 1k+-10k+ torrents count.
by Guest on 2025/09/01 01:31:50 AM
I think I've found an example of Tixati losing a feature completely because of its single threaded nature (instead of just lagging and hanging like hell when processing updates for big channels). User spring-bok has a channel with a test stream which includes audio and video, with data rate up to 150-200 KB/s (not Kb/s). One of my local machines simply can't process the stream fragments fast enough. One core is completely busy running Tixati, the rest are slacking off, and maybe once in a while it manages to grab a couple of consecutive fragments in time to send it to the player. Overall incoming traffic rate is also less than the announced stream rate. So if you have an old CPU, or a fresh one from the low GHz low TDP low spec range, there's a hidden limit (even though those processors can easily not just copy, but also fully decode the video stream).
I do understand that channels are experiment held by duct tape, and streaming is an experiment inside the experiment, but it is a nice curiosity.
It is possible that the source just can't upload data fast enough, but the local interface also gets very unresponsive during the tests. Stop the channel, and it is perfectly working once again. Audio streaming with smaller bit rate works fine, with less lag overall.
