Quote:
Originally posted by crohrs
Some users have noticed that LimeWire can take a while to hash shared files. Hashing is unfortunately a very CPU-intensive process. To prevent the hashing from consuming all the CPU, LimeWire actually does not hash files as fast as it could. Should we change this? |
but Personally, I think that the hashing feature is fine in its current implementation. I do agree however that there should be some type of progress indicator-indicating the file that is currently being hashed and its percentage of completion. Perhaps there should be a message indicating that files are being prepared for sharing. I have a particularly useful recommendation for CPU utilization and file-hashing:
1. Set to default hashing to 50% of the CPU utilization.
2. Create an option in the configurations menu that allows a person to change-on-the-fly the speed in which the hashing is done.
The first option allows you to satisfy the users who are happy with the current implementation and "Out of the box" configuration would support this implementation.
The second option, would give users such as myself the ability to allocate 100% of my CPU utilization to hashing. because I run several servants and the files can range in size from 1 MB to 400 MB in size and these files are stored on a network file server-- hashing can take hours.
Hope this helps.