I use Crypt over cache over Google drive.
My cpu usage is quite high when plex read files on the mount: (typically 200% to 400% CPU usage on my Atom C2750.
This means that the fact to read the file alorn, use half o my CPU power… This does not give a lot of space for transcoding…
Your config is kind of odd. The chunk size is huge so it’s pull 64M * 5 workers each time you do something. Any reason you have it so high? I was checking through my metrics and I have a i770 which is roughly 5-6x your CPU. I hit roughly anywhere from 5% to 25% of a single core. With that CPU, you aren’t transcoding anything really though.
Do you mean rclone is using 200%-400% of the CPU on its own? That does sound high…
Remember you are doing SSL encryption to speak to drive, then crypt’s own encryption so two lots. I wouldn’t have thought that should take too much CPU though.
Yes, this is exctly what i mean.
My cpu is not so weak (Passmark =3805) and rclone itself is using between 2 and 4 of the 8 core when i am reading a file on a crypted mount.
I am fully aware that there is some double encryption, but as you said, i was not expecting my server to put a knee down because of it.
Here is random screen capture of the situation: Reading the fils use more cpu than transcoding it ! That’s pretty unexpected.
First, thanks for the tip with htop . it’s much easier to understand.
Regarding the CPU horsepower: the issue is not related to transcoding. (anyway, i do directplay 95% of the time).
Transcoding is not an issue. Without rclone, With this very CPU i have already been able to transcode 2 x 1080p stream at the same time. (which make sense according to the recommendation of plex which is 2000 marks at passmark per 1080p stream. my cpu reach 3800 at passmark. I am well aware that this is not as good as your i7, but this is better than most i3).
Regarding the chunk size, i have tried a smaller one, (16M) , but it did not make any difference. For me it make sense to have a large chunk size for a plex library… considering the size of the file, i thought it was better to have a large chunck size.
Having larger chunks makes things slower as plex usually only need smaller pieces of the file to do certain things and any operation you have is going to grab 64MB every time.
The default chunk size for both plexdrive and rclone are set at 10MB.