Any way to quantify what causes a long library scan?

[podonnell 51]

I've recently been catching my library scans running, which I never have in the past. When I do. I watch to see how long it takes to complete. Currently I've had one running for at least 2 minutes prior to me starting this thread, and it is still be running when I finished typing this message.

I did check to confirm there is only a single stream happening, the CPU of the host machine is about as low as it normally is, and there are no current transcodes.

Curious if there is any way to quantify what might be causing the longer library scans as of late. Is there any way that this can easily be done?

Thanks!

[Luke 43166]

Hi, the log is the best way to see what it's doing. 

Library scan times will depend on what has changed since the last scan, what features you've enabled, what plugins you've installed, and what else might be consuming resources on the server at that time.

[bkettering 0]

Adding to what Luke said, the quick way to see it without reading the whole log: open Dashboard, then Scheduled Tasks while a scan is running, and look at which task is actually active and its progress. In my experience the scan itself is quick and the long part is the add-ons that run with it, like chapter image or thumbnail extraction and intro detection, especially right after an update when they reprocess things. Turning those off for a day is an easy test.