Super slow indexing. 4+ hours. Help!

ral_partha's picture
Submitted by ral_partha on Sat, 08/16/2014 - 20:36
Forums: 
Soulseek General Discussion

This has been asked before, but never really answered.

I have a very large collection (831gb, 159k files), and when I start Soulseek, it takes about 4 hours or more to index. Is there a way for me to disable indexing so I can index when I choose? (if not, this would be a GREAT feature) Maybe a certain disk optimization that I have been unable to discover during my research that can speed it up?

I have both the QT and the NS version, but I run 157NS13e 99% of the time, as I greatly prefer it to the QT interface. ANY help would be greatly appreciated. One other quick note, I am a supporter and not just a leecher. Over the years I've probably donated $75-$90 :-). I love Soulseek, use it a LOT, so will always support it. Plus, i enjoy gifting privileges to users whom I download a lot from.

I'd be happy to gift some privileges to somebody who can tell me how to correctly fix this! Really!

Here is my system stats: (Soulseek is on C: which is an SSD, but music files are on G:)

------------------
System Information
------------------
Operating System: Windows 8.1 Pro 64-bit (6.3, Build 9600) (9600.winblue_gdr.140330-1035)
BIOS: BIOS Date: 12/14/12 15:46:12 Ver: 04.06.05
Processor: AMD FX(tm)-8350 Eight-Core Processor (8 CPUs), ~4.0GHz
Memory: 16384MB RAM
Page File: 4961MB used, 13753MB available
Windows Dir: C:\WINDOWS
Video Card: NVIDIA GeForce GTX 660 Ti
Display Memory: 4037 MB

Drive: C: **
Free Space: 29.0 GB
Total Space: 121.8 GB
File System: NTFS
Model: SanDisk SSD SATA Disk

Drive: E:
Free Space: 1423.8 GB
Total Space: 1907.6 GB
File System: NTFS
Model: Seagate SATA Disk
Drive: G: **
Free Space: 983.6 GB
Total Space: 1907.7 GB
File System: NTFS
Model: TOSHIBA SATA Disk

Submitted by TJT on Tue, 08/19/2014 - 10:56.

I had this problem also with NS. It worked fine when I was using XP and older systems years ago, but once I upgraded to Vista/Windows 7-8 it took an eternity to index the files. It would no longer just update the new additions, but it would re-index everything from scratch. The attributes file would just start at 0 every time. I would even keep an older backup of the attributes file that helped a little, but it would still re-index almost everything.

I didn't like the Qt interface myself at first, but it eventually grew on me. It took me 4-6 weeks to adjust it. I have grown to love it, although it's still missing a few minor tweaks from NS that I miss. Qt indexes the files much quicker because it does it in the background. I think the quicker indexing of files alone would make it worth switching - not to mention all of the other extra features.