View Single Post
Old 18th August 2019, 20:41   #17153  |  Link
brumsky
Registered User
 
Join Date: Jun 2016
Posts: 116
I'm having an odd issue with ripbot. It's taking 5-15 minutes to start an encode chunk every time. I already did the update which compresses the lwi file down to around 30MBs.

Something I've noticed is that when the encoding client is starting a new chunk. The system process pegs my network connection - currently 1Gbps. While the disk usage is very low. So it'll start disk usage will hit 20-30MBps then drops to 1-2MB/s while the network is pegged at 800-900 Mb/s. it'll stay like that for quite some time. This is going from a R7 1700 to a AMD 3900x via Gigabit ethernet at the moment.

I've also confirmed the system running the encoding server matches the system process behavior.

I've also tried this on another machine same issue - 16c Xeon v4.

I understand that the lwi file is larger in general which takes it longer to copy. This seems abnormally long given the lwi file uncompressed is usually around 1.3GBs for a 4K movie.

Thoughts?

Last edited by brumsky; 18th August 2019 at 20:49.
brumsky is offline   Reply With Quote