7.6 scanning playlists is soooo slow

**MeSue** · 2011-07-24, 16:06

OMG, it is going to take almost as long to scan playlists as it took to scan the song files!

Code:

Discovering files   (27688 of 27688)   Complete  00:22:03
Scanning new files   (25383 of 25383)   Complete  02:40:54
Discovering playlists   (49 of 49)   Complete  00:00:12
Scanning new playlists   (15 of 31)   Running  01:11:21

Scanning my playlists in 7.5 took only about 15-20 minutes.

Anyone know how many more steps it does after this?

**MeSue** · 2011-07-24, 18:48

Code:

Scanning new playlists   (25 of 31)   Running  03:55:24

Seriously?

**JJZolx** · 2011-07-24, 20:22

Scanning new files isn't exactly a barn burner either.

- What are the specs of your server?

- Are the files on a local hard drive or located elsewhere on a network share?

- Are you using shortcuts/symlinks?

- How large are these playlists?

**erland** · 2011-07-24, 20:47

What type of rescan are you doing ? Is it a full rescan or just a rescan for changed files or changed playlists ?

How large is your playlists ? (number of tracks)

**MeSue** · 2011-07-25, 07:56

This was the initial scan that started automatically after installing 7.6. After 9 hours of scanning I stopped it before bed. It had been stuck on that one playlist for several hours.

I deleted a bunch of playlists, including some large ones that might have had missing files in them. Then I restarted the scanning, thinking it would finish overnight, but it only got 4 songs. My server does other things at night so that might be what interrupted it that time.

So just a few minutes ago I restarted SbS and kicked off another "look for new and changed" scan. Hopefully cleaning up the playlists folder does the trick. I still have some large ones, but they should not have any missing files.

There are no shortcuts or symlinks, and the files are all local to the server running SbS. Server is 1.8Ghz single-core, with 2 GB RAM. Scans on 7.5 used to take less than 2 hours for full scan, and 20 minutes or so for new and changed.

Third time's the charm... I hope!

**slate** · 2011-07-25, 08:47

Hmm sounds like a missing database index or something... anything in the logfiles?

Based on my own experience I would have thought that it would take 40-45 min for a complete rescan.

Are you game on trying a "clear and full rescan"?!

**MeSue** · 2011-07-25, 09:12

It stalled again so I aborted, did cleanup, and started over with a "clear and rescan." Seems to be progressing normally this time--so far.

**mherger** · 2011-07-25, 09:21

> It stalled again so I aborted, did cleanup, and started over with a
> "clear and rescan." Seems to be progressing normally this time--so far.

I guess it's too late to ask, but did you enable all the scan.* debugging?

--

Michael

**MeSue** · 2011-07-25, 09:31

Originally Posted by mherger

I guess it's too late to ask, but did you enable all the scan.* debugging?

No, didn't think of it, but I will if it fails again. It's about half-way through the second step (scanning new files).

**JJZolx** · 2011-07-25, 09:32

You should be able to just abort the scan again, set new logging settings and start over.

Keep in mind that in 7.6 (with SQLite) the server and library are completely usable during a full clear & rescan, unlike in past.

Thread: 7.6 scanning playlists is soooo slow

Thread Tools

Search Thread

Display

7.6 scanning playlists is soooo slow

7.6 scanning playlists is soooo slow

Posting Permissions