# Scan speed for analysis

**URL:** <https://forums.plex.tv/t/scan-speed-for-analysis/852900>\
**Category:** Plex Media Server\
**Tags:** server-linux\
**Created:** [September 8, 2023, 6:10pm UTC](https://forums.plex.tv/t/scan-speed-for-analysis/852900 "2023-09-08T18:10:57Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![smadenli](https://avatars.discourse-cdn.com/v4/letter/s/d07c76/32.png) [@smadenli](https://forums.plex.tv/u/smadenli)\
**Post date:** [September 8, 2023, 6:10pm UTC](https://forums.plex.tv/t/scan-speed-for-analysis/852900/1 "2023-09-08T18:10:57Z")

</div>

Server Version#:  
Player Version#:  
\<If providing [server logs](https://support.plex.tv/articles/200250417-plex-media-server-log-files/) please do NOT turn on verbose logging, only [debug logging](https://support.plex.tv/articles/201643703-reporting-issues-with-plex-media-server/#toc-1) should be enabled\>  
Is there are way to speed up scan sonic analysis by trowing more resources on the server?  
Also why not display the library being scanned and the queue?

---

<div class="post-metadata">

**Author:** ![ChuckPa](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/chuckpa/32/79710_2.png) [@ChuckPa](https://forums.plex.tv/u/ChuckPa)\
**Post date:** [September 8, 2023, 6:38pm UTC](https://forums.plex.tv/t/scan-speed-for-analysis/852900/2 "2023-09-08T18:38:01Z")

</div>

I can’t speak to ‘why not display’ but can ask Engineering

As for speeding things up / throwing more resources at it –

It’s a double edged sword and, no matter how you do it, you can’t please everyone

If we turn up the resources used - there will be those running low-end machines which will choke during playback because they WANT it to be a background task

If we turn it down (single thread) - where it is now, normal server operations aren’t impacted HOWEVER there will be those who want it done ASAP.

Not knowing the CPU you’re using makes everything guesswork but I suspect you have a CPU which doesn’t have a high per-thread Passmark speed and you’d rather have more threads running at the task ?

---

<div class="post-metadata">

**Author:** ![smadenli](https://avatars.discourse-cdn.com/v4/letter/s/d07c76/32.png) [@smadenli](https://forums.plex.tv/u/smadenli)\
**Post date:** [September 10, 2023, 4:12pm UTC](https://forums.plex.tv/t/scan-speed-for-analysis/852900/3 "2023-09-10T16:12:18Z")

</div>

I understand the issue re performance but why not make it adjustable by user at the GUI level – advanced tab maybe. I have ds1819+ loaded but I three are a few users. Especially at night there are no users. Would be convenient to increate the treats. I have Plex server running on ds1819+ with Inter ATOM C3538 which is not so powerful but more resources (more than one) is possible when there are no users.

If I have to it manually, It is a bummer but would still would like to know if let me know.

Sinan

---

<div class="post-metadata">

**Author:** ![BanzaiInstitute](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/banzaiinstitute/32/293273_2.png) [@BanzaiInstitute](https://forums.plex.tv/u/BanzaiInstitute)\
**Post date:** [September 10, 2023, 5:36pm UTC](https://forums.plex.tv/t/scan-speed-for-analysis/852900/5 "2023-09-10T17:36:53Z")

</div>

> [@ChuckPa](#):
>
> I can’t speak to ‘why not display’ but can ask Engineering

FWIW I think it would be very beneficial for Sonic Analysis to name the current track, just like we see track names zipping by in a library scan.

Sometimes SA gets stuck – though rarely these days, many bugs were fixed – and if a user can easily identify the troublesome track their next steps are much easier.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/plex/original/3X/2/a/2acb9765406f63293d357b4ec509ec39aa28f2ad.png) [@system](https://forums.plex.tv/u/system)\
**Post date:** [December 9, 2023, 5:37pm UTC](https://forums.plex.tv/t/scan-speed-for-analysis/852900/6 "2023-12-09T17:37:20Z")

</div>

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.