05-21-2012, 06:25 PM
Thank you for looking into this, Atom. The speed drop is pretty significant, but the larger host memory requirement is just a budget issue for those that need to do that level of auditing.
Would it be reasonable to keep the current 16 character maximum, low memory, high speed implementation, and then add support for either one or both of the other two options with a new series of hash types, so that the user can run at the highest speed/lowest memory requirements they need for the length set they're working on at the time?
Would it be reasonable to keep the current 16 character maximum, low memory, high speed implementation, and then add support for either one or both of the other two options with a new series of hash types, so that the user can run at the highest speed/lowest memory requirements they need for the length set they're working on at the time?