Sorry for the delay in replying. The numbers are derived from running a profiler on the code and looking at the amount of time spent in each call. For each XML-RPC call the time spent in MinML.parse() was about 60% of the overall time taken to complete the call, which is 150ms when not running a profiler. This was on a Pentium 1.8 with 768 Mb (somewhat higher spec than our target machine). Unfortunately the licence for the profiler has run out so I can't post the actual numbers.
I have also run the system with timing output sent to the logs and the results are about the same. I have completed the JNI wrapper for the C XML-RPC library and the application is much faster when using this. Subjective response time is now acceptable even on an Athlon 750 so we will be using the JNI wrapper from now on. Once our customers upgrade to higher-spec machines we will switch back to an all-Java solution again. Thanks very much for your thoughts and suggestions on this. Peter Butler On Fri, 2004-07-02 at 19:04, Jochen Wiedmann wrote: > Peter Butler wrote: > > > I've tried jprofiler and it told me that most of the time is spent in > > parsing the XML (about 150 ms with 60% of the time spent parsing). I've > > also tried other profiling tools but they are nearly impossible to > > install/use. > > Then I would like to see the numbers that make you conclude that the XML > parsing neds about 60%. > > > Jochen >
