Quantcast
Channel: Recent Discussions — Plex Forums
Viewing all articles
Browse latest Browse all 151235

plex-media-server-0.9.7.22 -- Scanning is quite slow

$
0
0

A short preface: I used Gsnerf's gentoo ebuild to install Plex Media Server, and it's sadly a bit outdated but I doubt this is the problem here.

 

After trying Plex on my main workstation, I was convinced it was the optimal media solution for my home network, so I set about installing it on my gentoo-based gateway/all around server. I've managed to set it up succesfully, but I'm finding that scanning files is a lot slower than it was on my workstation. Both server and workstation are similarly specced, however: an i7-875K on the workstation, an i5-3470 on the server. Both have 8GB RAM, and the only significant difference (other than the obvious OS difference) is that the PMS database resides on a SSD on the workstation and on a HDD on the server.

 

The real issue seems to be something in the way it accesses the database, because Plex Media Scanner.log is riddled with these warnings, especially when scanning music:

Aug 04, 2013 06:46:26 [0x3c56801c740] WARN - Waited one whole second for a busy database.
Aug 04, 2013 06:46:26 [0x3c55bfce700] WARN - Waited one whole second for a busy database.
Aug 04, 2013 06:46:28 [0x3c56801c740] WARN - Waited one whole second for a busy database.
Aug 04, 2013 06:46:30 [0x3c55bfce700] WARN - Waited one whole second for a busy database.
Aug 04, 2013 06:46:31 [0x3c560a2a700] WARN - Waited one whole second for a busy database.
Aug 04, 2013 06:46:32 [0x3c55bfce700] WARN - Waited one whole second for a busy database.
Aug 04, 2013 06:46:33 [0x3c56801c740] WARN - Waited one whole second for a busy database.
Aug 04, 2013 06:46:35 [0x3c56801c740] WARN - Waited one whole second for a busy database.
Aug 04, 2013 06:46:35 [0x3c560a2a700] WARN - Waited one whole second for a busy database.
Aug 04, 2013 06:46:36 [0x3c55bfce700] WARN - Waited one whole second for a busy database.
Aug 04, 2013 06:46:37 [0x3c56801c740] WARN - Waited one whole second for a busy database.
Unfortunately, the log doesn't provide any information beyond that short blurb, even with Verbose+Debug logging on. Searching for "busy database" on the forums yields surprisingly little results, so I wouldn't be surprised if this is caused by some configuration issue on my server. I just haven't the slightest clue where to look since the log doesn't provide any more information than that.

Viewing all articles
Browse latest Browse all 151235

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>