Re: Little optimization of JCEMapper

2004-04-15 Thread Erwin van der Koogh
I'm sure I don't have a vote, but I'd like to chime in and express my hope that these changes make it into 1.1. I ran some tests similar to Scott's and got good results: Anyone who contribute code or other stuff has a vote ;-) But these results are quite a bit better so I think Berin won't mind

Re: Little optimization of JCEMapper

2004-04-15 Thread raul-info
Thank you for including the code, it was a great honour. I'm currently working in other optimization, again in Transforms class, it seems that this class is invoked a lot(I´m optimizing a Liberty implementation, not based in opensaml, for Ericsson). The method ispublic Transform item(int i) is

Re: Little optimization of JCEMapper

2004-04-15 Thread raul-info
Thank you for including the code, it was a great honour. I'm currently working in other optimization, again in Transforms class, it seems that this class is invoked a lot(I´m optimizing a Liberty implementation, not based in opensaml, for Ericsson). The method ispublic Transform item(int i) is

Re: Little optimization of JCEMapper

2004-04-15 Thread Berin Lautenbach
Erwin van der Koogh wrote: But these results are quite a bit better so I think Berin won't mind including them in 1.1 ;-) GRIN. Nope. There is a new 1.1 in xml.apache.org/security/1.1 I have moved the first one into the superceded directory. Some stuff came up tonight that meant I couldn't

RE: Little optimization of JCEMapper

2004-04-15 Thread Scott Cantor
Thank you for including the code, it was a great honour. No, thank you. That rocked. -- Scott

Re: Little optimization of JCEMapper

2004-04-15 Thread [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote: Thank you for including the code, it was a great honour. I'm currently working in other optimization, again in Transforms class, it seems that this class is invoked a lot(I´m optimizing a Liberty implementation, not based in opensaml, for Ericsson). The method is:public

Little optimization of JCEMapper

2004-04-14 Thread [EMAIL PROTECTED]
Hi, Profiling a program that uses the xmlsec library I see that a vast amount of time is waste in translateURItoJCEID (in 86 times called a 4sec of 22 sec that the whole program time). I made a little cache in order to not parse and xpath search the config.xml node in order to find the

RE: Little optimization of JCEMapper

2004-04-14 Thread Erwin van der Koogh
Heh, is there time to get this into 1.1 since it's not officially out yet? I don't know. I don't particulary like to make changes to it, but if this turns out to be a decent improvement I think we should give it a try. I didn't have time to properly test 1.1 until tonight and I did most of the

RE: Little optimization of JCEMapper

2004-04-14 Thread Scott Cantor
Scott, could you try and see if you can get some feel for the speed increases? They don't have to be perfect, but rough estimates would really help to make a decision. I've got a copy of the 1.1 jar in our cvs now. I can try to get some timings on SAML signing with that and then do a build

RE: Little optimization of JCEMapper

2004-04-14 Thread Berin Lautenbach
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. Wow! It's interesting in other respects too. The library makes extensive use of XPath calls all over