I think John Aronson wrote: > The profiler reports that that almost all the execution time is spent > loading classes. I'm hoping that fact means that there's something wrong > with my code which I could fix to improve the performance.
It does look like a lot of time is being spent loading classes during calls to "definstance" and something in ReflectFunctions; these are clearly your application classes that Jess is, for some reason, loading very slowly. I suspect this is a "microbenchmark", and the problem may just be that loading your classes is intrinsically slow -- for example, the first Swing class loaded can often take a really long time because it can drag in hundreds of other classes. In that case, I'd say you should just run the thing 50,000 times instead of 1,000 times, and see if the class loading time doesn't disappear down into the noise (because it only happens once.) Based on your description, your benchmark likely takes only a fraction of a second to run, discounting the JVM startup time and any anomolous class loading behavior. But in any case, Jess doesn't define its own class loader, or do anything odd that would force the same class to be reloaded multiple times. --------------------------------------------------------- Ernest Friedman-Hill Science and Engineering PSEs Phone: (925) 294-2154 Sandia National Labs FAX: (925) 294-2234 PO Box 969, MS 9012 [EMAIL PROTECTED] Livermore, CA 94550 http://herzberg.ca.sandia.gov -------------------------------------------------------------------- To unsubscribe, send the words 'unsubscribe jess-users [EMAIL PROTECTED]' in the BODY of a message to [EMAIL PROTECTED], NOT to the list (use your own address!) List problems? Notify [EMAIL PROTECTED] --------------------------------------------------------------------
