Watcher, be more efficient in regards to hard drive throughput
Feature details
When adding, i have noticed that vidcoder does not take into account hard drive access.... it would be great if vidcoder could be a more more gentle, for example when queuing, and vidcoder is also scanning for forced subtitles, then wait for queuing, allow the encoding job to start first before hitting the hard drive with another intensive throughput job.
thanks.
So you're saying, if a large chunk of scan requests come through the Watcher, wait until they're done before starting the encode. It would mean less skipping back and forth between read locations, which would help a mechanical hard drive. Sounds like a good enough change; I just don't know when I'd have enough time to implement it.
Exactly, your words better than mine
Sent from Outlook for Androidhttps://aka.ms/AAb9ysg
From: David Rickard @.> Sent: Saturday, January 13, 2024 5:47:36 PM To: RandomEngy/VidCoder @.> Cc: Registered55 @.>; Author @.> Subject: Re: [RandomEngy/VidCoder] Watcher, be more efficient in regards to hard drive throughput (Issue #1206)
So you're saying, if a large chunk of scan requests come through the Watcher, wait until they're done before starting the encode. It would mean less skipping back and forth between read locations, which would help a mechanical hard drive. Sounds like a good enough change; I just don't know when I'd have enough time to implement it.
— Reply to this email directly, view it on GitHubhttps://github.com/RandomEngy/VidCoder/issues/1206#issuecomment-1890614596, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A3JPIELEKRFOONTOD4PPBUDYOLCDRAVCNFSM6AAAAABBT3GJGWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJQGYYTINJZGY. You are receiving this because you authored the thread.Message ID: @.***>