yadayada
acd_cli slow on read
Hi, I'm using a dedicated Windows server with a VM where I installed acd and Plex Media Server.
I have problems during Plex streaming: 'top' command shows acd_cli process high CPU usage (60%) but the 'global' CPUs usage is 20%. Windows Task Manager show 26% from the VM (I gave it 4 of 8 cores). http://imgur.com/hsi6W3m http://imgur.com/PwtFThQ
From Windows task manager download speed is very slow: 900Kbps for most time and then for a few seconds it goes up to 80MBps, then came back to 800/900Kbps and Plex is continuously buffering. http://imgur.com/XRSIWEV http://imgur.com/IAPp5bH
But when I try to use acd_cli dl it goes up to 40MBps. So I don't think is a problem with connection speed.
I have a Xeon E3 1225v2 and I gave VM 4 cores (out of 8) and 4GB of RAM. My disk is a mechanical HDD (unfortunately they don't have SSD). My connection is 1Gbps / 250Mbps
Can you help me understand why it seems that acd_cli is very slow on reading files?
Thanks,
Luca
A minor optimization was done for the read performance recently [minimizing database access]. If you have not upgraded in the last weeks, please do so.
(I gave it 4 of 8 cores).
Unfortunately, (C)Python with multithreading cannot utilize more than 1 core ATM.
From Windows task manager download speed is very slow: 900Kbps for most time and then for a few seconds it goes up to 80MBps, then came back to 800/900Kbps and Plex is continuously buffering.
But when I try to use acd_cli dl it goes up to 40MBps. So I don't think is a problem with connection speed.
You will have to examine the access patterns of Plex in FUSE (see the documentation). If Plex reads files in a non-sequential manner (which I presume it does), a new request must be issued for each new read offset, which takes time.
You will have to examine the access patterns of Plex in FUSE (see the documentation). If Plex reads files in a non-sequential manner (which I presume it does), a new request must be issued for each new read offset, which takes time.
In terms of random (non-sequential) reads, is the 800-900Kbps speed an expected value because of the request latency?
