Re: Security Performance issue

2010-07-24 Thread Deven You
I am not sure which classes are loaded during the Security.getProvider() for both harmony and RI, and I found another interesting thing that is the time spent on Class.newInstance() on both harmony and RI are almost the same though the time on the Class.forName() are different so much. 2010/7/24

Re: Security Performance issue

2010-07-24 Thread Deven You
Hi Tim Actually I mean Class.forName() in theSecurity.getProvider() invocation stack. So I can be sure our security implementation loads much more classes than RI's one. Thanks for your question, I think on the above mail I talked so generally. 2010/7/24 Tim Ellison > On 22/Jul/2010 11:42, Deven

Re: Security Performance issue

2010-07-23 Thread Tim Ellison
On 22/Jul/2010 06:07, Ray Chen wrote: > Hi All, > I found that our security implementation is much slower than RI's when > get an algorithm instance. > I have done some investigation and found that most time are consumed > on loading and initialising providers. > Following is the test cases and res

Re: Security Performance issue

2010-07-23 Thread Tim Ellison
On 22/Jul/2010 11:42, Deven You wrote: > Profiling results show RI's Class.forName() takes much less time than > Harmony ones. It may caused by harmony load too much classes, maybe we need > consider load providers only needed. You mean "Class.forName()" loading the same class (i.e. the time to se

Re: Security Performance issue

2010-07-22 Thread Deven You
Profiling results show RI's Class.forName() takes much less time than Harmony ones. It may caused by harmony load too much classes, maybe we need consider load providers only needed. 2010/7/22 Regis > On 2010-07-22 14:26, Ray Chen wrote: > >> Hi Regis, >> You mean init these providers is slow, r

Re: Security Performance issue

2010-07-22 Thread Regis
On 2010-07-22 14:26, Ray Chen wrote: Hi Regis, You mean init these providers is slow, right? But actually we should not init unnecessary providers. I added some info in our code as following and you can see init these provider takes most of the time: ... long start = System.currentTimeMillis();

Re: Security Performance issue

2010-07-21 Thread Ray Chen
Hi Regis, You mean init these providers is slow, right? But actually we should not init unnecessary providers. I added some info in our code as following and you can see init these provider takes most of the time: ... long start = System.currentTimeMillis(); p = (Provider) Class.forName(providerC

Re: Security Performance issue

2010-07-21 Thread Regis
On 2010-07-22 13:07, Ray Chen wrote: Hi All, I found that our security implementation is much slower than RI's when get an algorithm instance. I have done some investigation and found that most time are consumed on loading and initialising providers. Following is the test cases and results to sho