Question about indexing

thescarletfire's picture

Hi there,

I have roughly 100,000 files that I share on SoulSeek and everytime that I reboot my PC, and restart Soulseek, it takes almost an hour to re-index. Now, my question is two fold please:

1) Are files available for download immediately after I hit the share folder button (i.e users browse my shares and can see files - they say they can, while I'm still indexing)

and

2) Where does SoulSeek keep it's index? Like, is it possible for me to "backup" the index of a certain collection of shares (which never changes) so I can just reload it quicker? Is there any way to disable fully or speed up the indexing?

Thanks!

Is this with SoulseekQt or the original Soulseek client?

thescarletfire's picture

Both clients, though QT takes significantly longer. For example, no files have changed so it's 100% the same files every time I boot up SS. QT indexes 100k files in about 45 minutes, and original SS does it in about 30 mins. My friends who share the same or more files never have this happen - can you perhaps troubleshoot this? Thanks Nir! Rock on.

PS. I checked the cfg files and they look correct (size-wise, and contents). So I'm not sure whats going on. My PC is a custom i7 build w/ plenty of power and RAM, if that helps. Win7 x64

Does SoulseekQt not actually start until the files are done indexing? Are these files on network storage?

"My PC is a custom i7 build w/ plenty of power and RAM, if that helps. Win7 x64".

Ah. Perhaps this is where the processing delay comes from. On Linux, we can choose between the x86 and the x64 builds, whereas you Windows users only have the 32bit build to play with. And running 32bit on x64 usually works, but still, it may take some sort of "creativity" from OS's side sometimes, "eating up" some more CPU cycles.

thescarletfire's picture

Hmm, I'm not sure it's the x64 - I tried this on Win7 x86 this weekend it's worst. It took 80 minutes to scan 150k files using QT and 40 minutes to scan the same files using NS.

Just letting you know in case it helps as you further develop SoulSeek.

The files are on both an internal SATA HDD and an External USB2 drive, local. SoulSeekQT 'starts' during indexing but I wasn't sure if files were immediately accessible or not.

thescarletfire's picture

Hi Nir,

Random question(s) for when you crave some brainstorming :)

First off, is there any other way to donate other than PayPal? I'd love to send some support your way for all this but I'm not a PayPal guy currently, sorry.

Sorry in advance with the whole "picking your brain" approach in this post, but as I've said before - Soulseek is a huge part of my life and you are the BEST. This community is just epic. My music career I owe a LOT to Soulseek for, really. You are the man.

*I have several hidden Soulseek-client files - do I need to keep all of them, they seem to auto-save at random times. Is it safe to delete the older ones and just keep the most recent one? Perhaps this is why my client locks up constantly? (since I have 5-6 client-data files with various numbers after them ala renaming incremental backups). Would I lose all my data and users if I delete only the older files and not the last modified one? Every time I close Soulseek and reopen the client (even sometimes every hour automatically also), it seems another 20MB client-data file appears - that will add up fast - is it safe to remove all older ones? or...will all be lost?

*I have 8GB RAM, but I believe SoulseekQT is an x86 app, right? So my extra RAM is useless to help with SoulseekQT's workload? Should I stick with Ubuntu x64 if I would like to use 8GB RAM for my Soulseek fun? :) Any options for Windows 64 users?

*Would extra RAM even help at all speed scans/indexing up for Soulseek? Would USB2 external drives index/MP3 scan much slower than internal SATA drives?

*For what it's worth too, perhaps ironically for me at least, SoulseekQT NEVER crashes per se, - EVER - but it always gives me the "Not Responding" when scanning my 150k files, or overnight sometimes during idle times the program locks up and I have to restart it. I then have to quit Soulseek, rename the shared folder in Windows (so it doesn't see it upon launch), then Soulseek starts fine, then RE-add that folder in Soulseek.

-Scarlet

*Recently edited because I realized/figured out a few things since I had first posted this novella of a post ;) Rock on Nir!