As you can see on chart, md5 hashing time almost independent from file size, therefore fingerprinting will depend mostly from your server configuration.
On Thursday, November 8, 2012 10:09:27 AM UTC+2, AdvanTiSS wrote: > > Fingerprinting process based on md5 checksum calculation > using java.security.DigestInputStream on each file targeted for > fingerprinting. > You can read some information about md5 algorithm performance here - [Secure > hash functions in > Java<http://www.javamex.com/tutorials/cryptography/hash_functions_algorithms.shtml> > ]. > > On Wednesday, November 7, 2012 3:44:11 PM UTC+2, qazwart wrote: >> >> How resource intensive is fingerprinting? What if I fingerprint all files >> that I build? >> >> We deploy a lot of zipped archives instead of jars and wars in our JBoss >> instant. This way, we can generate various client configurations. However, >> it also means that the build assets can get moved around quite a bit, and >> I'd like someway of determining what build that file was associated with. >> Right now, I'm just fingerprinting the zipped archive, but it may be better >> if I fingerprinted all the files inside the archive before it is zipped. >> >> I can't imagine fingerprinting taking up a lot of resources, on a per >> file basis, but if I am fingerprinting hundreds of files per build, I can >> imagine it being a problem. >> >> What is your policy on fingerprinting files? > >
