I have no interest in a per user cap, but am interested in a global cap for uplink speed. This is particularly important using cloud sync, as it cannot be controlled as on-demand viewing can.
I also really would like to see this feature implemented. Either a individual bandwithlimit per user or a global limit per shared user (excluding the owner of the server).
I also really would like to see this feature implemented. Either a individual bandwithlimit per user or a global limit per shared user (excluding the owner of the server).
It is bigger than just sharing. It should be a upload limit for Plex overall, including clients, uploads to cloud sync, etc.
+1
I would also like this.
I would also like to see a limit on logins per shared username.
This would be great to have. I wouldn't have a need for a configureable cap for each user (although I would use it if that feature was available), but would love to see a global bandwidth cap (i.e. all Plex remote clients combined should not exceed 8mbps) and a quality cap for all remote clients (i.e. any remote client cannot exceed the 3mbps quality preset).
I would really like to be able to control each user, or even better, groups.
For those of us using Linux, rudimentary traffic shaping is available via the 'tc' command: https://forums.plex.tv/topic/39823-howto-limit-plex-media-server-bandwidth-on-linux/?p=549834
I wanted to check back in on this and respond to some of the posts. First, thanks mrbubbles02, for pointing out the traffic shaping options. Unfortunately, it's simply too annoying to be considered a viable solution.
I see a lot of people wanting both per-user, global, and group settings. I feel like ultimately the global setting is probably the easiest, and that per-user is next easiest, and per-group limits require a higher level of work (with the understanding that groups as entities would have to be created, since they do not exist currently). However, I do not see why, given a bit of work, all three wouldn't be possible and even preferred to any one option presented individually. A global limit could then apply to all connections while still allowing per-user/per-group settings that limit individual connections. I could then imagine a situation where three people with their individual limits put together hit the global limit. In which case, a fourth person trying to connect would simply receive a "server busy" message.
That then gets into issues of giving certain users priority, and while I'm not asking for that now, I could see it being beneficial in the future. I just imagine giving access to someone like my brother in-law who might occasionally want to watch something, but I'd only do it if I knew he wouldn't prevent more "important" users from accessing content. Also, if I were a remote client, and everyone was already maxing the global limit, I'd want to have the option to butt in and use my server—either by lowering their quality settings, or booting someone until load goes down.
Anyway, just some thoughts.
Please implement this!
This is definitely a MUST HAVE feature.
I really need this.
If we even had the ability to simply cap the number of concurrent Remote Users that would help as a stopgap. I know the general number of users I can handle at the same time. If the system simply would not allow another remote user to connect until below that limit, it would help everyone's experience, in my opinion.
It always bothers me when Remote Shared Users have been watching something for a while, then more people connect, going over my upload bandwidth limit, and it ruins all of their experience. It would be helpful if the system at least allowed us to manage Remote Users on a First Come, First Served basis by setting the number of concurrent connections we feel we can allow. Then just send a simple message to any clients who try to connect after the limit has been reached telling them that the server has the Maximum number of remote connections allowed, and to try again later. That's gotta be easier than the PMS trying to track actual bandwidth usage and cutting off Remote Users that way.
Running my server on a 2011 i5 with a very basic Comcast internet package, my #1 feature request would be to be able to limit the transcoder's CPU utilization so I can still use my machine while it's transcoding (I'm currently using a free app called "AppPolice" to do this, limiting to 250% CPU utilization) and limit it's upload bandwidth utilization. I can't even get a webpage request in edgewise while Plex is uploading video.
please please please plex gods impliment per user rate limiting please :)
This would involve some significant modification of PMS and Plex/HT (in that the quality settings in Plex/HT would have to grey out for qualities above the cap)
I don't think you have to go that far on the client side... let the client pick whatever speed they want, if it's greater than what the server allows the server just sends the higest allowed speed...
*double post*
+1
Also for people (like me) who only have a 2mbs upload, and at times 2 people watching remotely...
I definitely want to limit the number of concurrent streams per account. Say a shared account has three streams going on because they have multiple streams going on at the same time. I want to prohibit that to a single allowed stream at a time. Sort of like how Netflix only allows so many concurrent streams per account.
+1
Upvote this thread as well. Not *exactly* the same, but almost.
+1
Cannot use the plex.tv web app with my 1mbit/s right now. This needs a fix!
