I've tried out syncing for the first time to my Nexus 7, and realized that while streaming with the block based encoding uses all my server's CPU cores, when using sync, it's single threaded. Even though I'm syncing 10 episodes of the show, it goes sequentially, single threaded. Is this intentional, or just left like this for ease of implementation? Would make sense to at least start multiple encodes in parallel IMHO, as even with server grade Xeons the single thread performance is nowhere comparable with using all cores, let alone all sockets+all cores.
I have the same situation. I am running a dual xeon setup (2 5620s). It would be much be faster if it would use all 8 cores or at minimum the 4 cores of one cpu. I get 40-50% usage one a single core when syncing at the highest setting to my iphone. source is 1080p mkv container. not sure on the audio off the top of my head.
I have noticed this also. I am running it on Ubuntu Server 14.04 with 2 xeon cpus and 16gb of ram. I am trying to sync to my laptop for when I am at sea. This servers only purpose is for Media. It is running Plex, SickRage, CouchPotato, Headphones, Transmission, BitCannon and Jackett… That is all. I would like it to use a lot more cpu. It is set to make my cpu hurt but it doesn’t look like it’s in pain! It is using 1 core when I have 2 cpus with 4 cores each…
Maybe there could be an option as to how many cores Plex will use? And it could spread the workload for sync across those cores?
I know everything on my server could be run on just the one core and save all the rest for Plex.
Just realized the same problem too as I prepare my kid’s iPads for an upcoming trip. I am running a 5960X on my server and would expect MUCH faster encode times. I am only seeing 25-30% utilization which seems completely absurd given the amount of resources available. Takes upwards of an hour to transcode a single BD video, whereas Handbrake can do the same video in less than 20 minutes with similar settings. Poking around in the server settings doesn’t reveal any hidden transcoder settings to open up performance.
I really hope the Plex Team considers making this an area of user configurability. As the current setup is a waste of both my server’s capability and my time.
Yep - getting the exact same behavior. Debian 8 (Jessie), PMS v1.5.2.3557 running on a Core 2 Quad. Would expect better than this out of the usually awesome Plex team.
Any update on Plex only using 1 thread? I have 36core/72thread dual xeon workstation and it just feels silly that plex only uses 1 thread. Anyone from Plex read these messages at all? Years with no replies…
Sync is considered a background task. It is for that reason Engineering decided to resource limit it as they do in order to prevent interference with live streaming tasks.
Couldn’t you nice the task in linux or similarly in windows? Could also provide an option to use all resources as toggle for users with dedicated hardware.
Been requested of Engineering. We keep asking nicely. Unfortunately, we’ve not had enough Feature Request votes to get their attention .
I just don’t understand this. Not allowing Mobile Sync transcodes to utilize more than 1 thread makes the feature all but useless. If a user tries to sync 2-3 movies or an entire season of a show there’s about a 99% chance it will never happen. It will take hours to complete the conversions and by then their device has either gone to sleep or otherwise no longer connected to Plex. This means the user has to then go back into Plex to do another manual sync to start the download of all the files which can take hours itself. It’s just not workable. Plex might as well just get rid of the Mobile Sync feature if they are not going to give server owners the ability to actually utilize our server hardware.
Where can we vote? Is there a thread that seems like the “master” for this issue? Seems like this is one of the key reasons why sync doesn’t work for lots of people, including me with an 8 core machine putzing around at a measly 3x-4x a lot of the time. Other reasons include having to babysit the whole process and hit refresh all the time.
It is using 1 core when I have 2 cpus with 4 cores each…