4017/60,000 files shared
 

Why does it take so long to share files, and why does it unshare them, then reshare 1 at a time very slowly when restarting Limewire?

4020/60,000

4023/60,000

So you can see how long it takes...

What the f.. are you asking or saying!?! http://users.pandora.be/eforum/emoti.../crazy/083.gif http://users.pandora.be/eforum/emoti...crazy/1148.gif

Well I don't think the 2nd and 3rd post where necessary. But I think this what your asking:confused:

When LimeWire start it is doing several things at once. 1) connecting you to the G network 2) sorting and indexing your shared files, so other users can see them to d/l, 3) trying to connect any d/l you may have had 4) starting to u/l when other users want to d/l from you.

It takes LW time to do this, and the more files you share the longer it will take

Other factors that will affect this are the resources you have available for LW. Like How much RAM you have or your CPU speed.

On this system. It takes appx. 13 - 17 for LW to settle down and stablize. Once it has LW operates very, very well. I'm running LW Pro 4.4.5 and JRE 1.5.0_01

Sometimes you just need a little patience.:)

Hi, thanks for your answers.. but 5 minutes to index 3 files??

Is it creating a 10mb file for each file I share or what?

Are you refering to the Describe function? It should not take long at all. If it does then it says something about your system. Like it or not! ;)

well I guess you must be running 256 MBs RAM@133 Mhz on a 800 Mhz processor with a front side bus of 133 Mhz and slow hard drives. I think that is a fantastic speed.

If your going to ask a question or make a comment provide some information.

Read the "Sticky Newbies guide to wrighting a good thread"

No No No ppl :eek:

LimeWire calculates the so called SHA-1 Hash value for each file. In short, a Hash is an unique fingerprint of a file which identifies it among billions of other files on the net.

http://en.wikipedia.org/wiki/Hash_function
http://en.wikipedia.org/wiki/SHA_family

... it's a cryptographic process with a lots of math and there's absolutely no way around it. The slower your computer is the longer it takes to compute the Hash (a dual 2GHz G5 with one CPU maxed out for the Hash function can process for example 70 to 80MB/s and an iBook G3 with 500MHz IIRC 15MB/s -- but the hash function is running in a throttled mode in LW to not eat up all CPU cycles).

AMD Athlon XP 3000+ ( 2.2ghz - faster than friends p4 3.0ghz )
768 MB DDRam

Runs Hl2 flawlessly with full settings, Doom3 too, highest resolutions on both..

.. But it is on D:\

Both discs are defragmented...

I think not on the speed, but you obviously need to do some research, because you only saw the specs you wanted. Hint - hardware clock speeds and how it effects software.

rkapsi makes a good point and explains well why it takes LimeWire time to load.

But as an after thought-If you want a machine that does fantastic number crunching you should switch to a Mac. They've run circles around PCs for years in that aspect.

Patience is a virtue

As I said, the hashing process is running in a throttled mode. On my G5 approx. 10MB/s => ~600MB/minute. You haven't said how large your files are...

Well, and HL2 and Doom3 have nothing to do with cryptography (former make heavily usage of the GPU - in fact they're known for their excessive usage of the GPU - and the latter is a CPU only process).

60,000 files - pieces of work I created totaling near 170gb...

It feels like its doing 10mb/s

It feels like 10 mb/s...

On Direct Connect it hashed them at over 100mb/s

So... how many files does LW does still need to compute SHA-1? Maybe you should let LW do that in a night (wow 170gb shared, you are really a DC user...). Anyway, welcome to you and your files onto the Gnutella network!

:D

Hi, thanks for the warm welcome :-)

Leaving it on overnight got 16000 total done - then it had a problem, had to restart LW :-/

Well, still no luck - leaving it running all night - its still not done and it encountered 3 problems while running... File hashing did not recommence properly..

Would it be possible for the LimeWire developers to make a small tool that hashed the files and created the database so when you start LimeWire they are automatically shared?

It takes 10 mins for my shared (2.5 k files) to load. It depends not only on the no. of files but also the size of the files & the speed of your computer, & I suspect version of LW & OS. It took much, much longer to load half as many of the same files in Mac OS9 compared to OSX on the same computer.

Your suggestion sounds good. I don't know the practical sides to it.

I would try to separate files in folders of 1000 files to isolate the file that makes LW crash.

Problem is I have all files sorted already..

Practical use of the tool I suggested would basically allow users to hash/share the files before opening LW - If there is a file that has a problem it would tell you which one...

Super slow indexing
 

Well this is truely disappointing. A real bummer.

I have 302 episodes of The Simpsons (27GB), which is Seasons 1 -> 13.

I have 3,595 MP3's (16GB) organized neatly in albums, and I have a whole whack of other fun stuff (~11GB) which I have selected to share.

I'm using LimeWire 4.8.1 (free). My computer is a P4 1.6GHz with 256MB RAM... and evidently it's simply not up to the task. After far too many hours of everything lagging, I'm through 1300 files... about 1/3.

I want to share these things, but I'm going to be forced to share just a tiny amount, only enough to hopefuly not be a "Freeloader". I use my computer all day, and through much of the night, and if I must compete with LimeWire's indexing each time it starts up.... well, it's just sad. Something really really needs to be done.

dkd