Some owners of Emby have looked at the logs and found that using Infuse will cause a large number of unnecessary requests, and when the number of users is too large, it will cause a lot of load on the server, and the development team may be able to see what the problem is and solve it, making Infuse more convenient
Here’s some feedback on this issue
Infuse/* Frequent requests
It is not recommended to use infuse, this software will cause a large number of requests in a short period of time (I don’t know what to order) At present, there is a limit when the number of requests is reached, and it cannot be played directly, and it will not be automatically unblocked
When there are too many people using an Emby server at the same time, Infuse will have multiple requests during playback, and when there are 2-4 threads or more threads downloading the video at the same time, it will cause the Emby server to lag, maybe the team can optimize this problem, such as using a fixed thread (2-3) when playing videos, which can greatly relieve the pressure on the server, so that Infuse can be more suitable for a large number of emby servers
The following is the original words of the emby service owner:
“Infuse means that there are many requests during playback, for example, when a video is played normally, one thread is downloading the video, and infuse is when 2-4 or more threads are downloading the video at the same time.”
Infuse is able to connect to Emby in different ways, and depending on the connection type will make use of a few different user-agent types, with each having varying impacts on your server load.
For example, connecting Infuse to Emby in Library Mode will result in many more requests compared to Direct Mode. And allowing file downloads can lead to more bandwidth usage compared to just streaming.
If you are a server admin, it may be possible to limit or block certain user-agent types by adjusting various settings on the server.
Details on the user-agent types Infuse uses when connecting can be found in this guide.
For users, most of them use the infuse-direct mode, and the caching uses automatic, and the problem is that most players play in a single-threaded way, but infuse seems to be multi-threaded (maybe 4 threads?). The upside is that the caching speed is much faster compared to other players, and the downside is that when the number of people increases, the load on the Emby server is also increased! Maybe you can consider fixing the number of playback threads for infuse (e.g. 2-3 threads). Among some emby server owners, there are some cases where infuse is frequently banned due to the country of the request, so you can look at this problem