My content is all local to a single backend. It's not striped across an
array, it all lives on two 5400rpm spindles. Maybe the issue is volume?
It takes me about 35 seconds to rescan 15k pictures, 15k mp3s, and 10k
video files. <br><br>As Mark mentioned, linux caching could be the reason some scans are much faster - if I clear out the cache (by rebooting or with echo 1 > /proc/sys/vm/drop_caches) the scan takes about 5 minutes to finish. I wish there were a command line way to initiate the scan - I could run my own script to look at the 'new footage' folder and rescan when I see new files.<br>
<br><br><div class="gmail_quote">On Sun, Mar 25, 2012 at 7:13 PM, Mark Lord <span dir="ltr"><<a href="mailto:mythtv@rtr.ca">mythtv@rtr.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On 12-03-25 07:07 PM, Raymond Wagner wrote:<br>
> On 3/25/2012 18:27, Joe Mythtv wrote:<br>
>> is it possible to run a 'scan for changes' of the video library in the background? it can take<br>
>> several minutes to run so it is obtrusive to run everytime i upload home videos to my DVR (when<br>
>> family members want to see footage of the kids, they want it ASAP...)<br>
>> maybe there's a way to run it only for a specific directory to which I upload files more frequently?<br>
><br>
> With a few thousand videos spread across multiple drives and arrays, performing a scan of the Video<br>
> Library only takes me a couple seconds. Any new content added needs to be hashed, but you're<br>
> talking about reading 64KB from the front and back of a file. Not something time intensive for even<br>
> dozens of new files. If you have the batch metadata grabber enabled, that can take some time<br>
> churning through the new content, but that is run in the background and is going to turn up empty on<br>
> home videos anyway.<br>
><br>
> If your scans are taking several minutes to run each time, there is something misconfigured on your<br>
> system. Is this content local to one of your backends, or on a remote network share? There is a<br>
> known issue where CIFS shares, and especially deeply nested ones, take an inordinately long time to<br>
> scan.<br>
<br>
<br>
</div>The first scan after booting may take some time.<br>
After that, the kernel will have much of it cached<br>
for future scans, depending on VM activity.<br>
<br>
So it's not always mere seconds. Here, it seems to take about 30 seconds<br>
to scan about 2400 videos. Subsequent runs take perhaps 2-3 seconds.<br>
<div class="HOEnZb"><div class="h5"><br>
_______________________________________________<br>
mythtv-users mailing list<br>
<a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br>
<a href="http://www.mythtv.org/mailman/listinfo/mythtv-users" target="_blank">http://www.mythtv.org/mailman/listinfo/mythtv-users</a><br>
</div></div></blockquote></div><br>