I looped over a Junit test I put into OpenSAML that reads in a SAML assertion, signs it (RSA/SHA1), dumps it, reads it back in, verifies it, and takes a time reading. Since the whole thing was CPU bound, the numbers are practically identical across runs.
I used my laptop, a 1.8 GHz with 512MB, XP, JDK 1.4.2 and did 100 loops. This is with the Sun JCE built in, not BC. For completeness, I ran a test with the 2.0 jarfile that was sitting in CVS from way back. "2.0" fake release: 840 ms avg 1.1 RC Berin put out: 915 ms avg Build of CVS Head: 540 ms avg Seriously. Maybe I'm just a special case and the patches target my use case, but, wow. -- Scott
