There is no such thing as xml security benchmark, I try to do one myself several time, but the lack of time always made me postpone. In order to test my changes I use a slightly modified copy of the old xmlbench, it only tests inclusive-c14n and enveloping signatures. But it works for seeing what can be optimized. I also test again time completion of our test suite, but this becoming more difficult. Because it use to take 120 seconds to run, now it only takes 2-3 and the speed improvements are harder to see.
You can also try a loop of several thousands verification and decoding. So you can try to measure the speed up. If I can help you, don't hesitate in asking. Regards, Raul On 4/7/07, jason marshall <[EMAIL PROTECTED]> wrote:
There's a spot in the MessageDigest calculations where all but one path through the code doubles up Buffered I/O and Block I/O. I've been working on a patch to hoist the buffering into the one path that needs it. This gives my path a nice little throughput boost, but I'm wondering if I've caused regressions along the other paths. Raul, do you have a set of benchmarks you were using when doing the 1.4 tuning work? Before I try to push a patch through the complicated IP system at work, I'd like to have an idea if it will get accepted or not. -- - Jason
-- http://r-bg.com
