Quote:
Originally posted by LeeWare
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. |
I Agree With LeeWare And Believe there Should be options to change the hashing priority rather that a pre-defined rate.
But As David Said
Quote:
Originally posted by David91
The more choices you give the user, the steeper the appearance of the learning curve and the greater the need for proper documentation to explain the whole system. I favour leaving this aspect alone. Hashing is often quite slow because I rarely have Limewire standing alone but once you learn not to mess with it once it has started, I just get on with other things until it has finished. I don't think this aspect is broke enough to need fixing. |
It Could Confuse the users, So how about This :
1. The hashing priority is selected as the way it currently is. But you can select the hash priority to be higher and a short description about the priorty you selected would appear So people can make a informed decision