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...