Yes I agree with Nabeel. We need to figure out why our performance is low when the data sizes are large. At the surface level it seems that it has nothing to do with the Axis2/C engine when compare to the Axis2 Java. Also when the data sizes are large httpd itself may get slow.
Another important thing is we need to see why guththila is slow when it comes to large data sizes. My guess is the buffer mechanism used in the guththila_xml_parser is causing this. But need to investigate this properly using a profiling tool. Thanks, Supun.. On Sun, May 11, 2008 at 9:03 PM, Nabeel Yoosuf <[EMAIL PROTECTED]> wrote: > It's encouraging to see the C implementation performs well. > > As per the graphs, the performance gap between the two implementations > implementations (Java/C) and between the two parsers (Guththila/Libxml2) > narrows down as the data set size increases. There could possibly be two > reasons for this. > > 1. Increased bandwidth utilization (as indicated in one of those graphs) > adds more network latency. > 2. The engine is less efficient in processing large data sets compared to > small sets. > > It would be interesting to see which of the above two is the dominant > factor. > > If it is the first one, one approach may be to introduce message > compression techniques for large data sets further improve performance. If > it is the second one, one possible direction is to see if the same data set > is repeatedly processed and take preventive actions (e.g. caching, > annotations, etc.). > > Thanks, > Nabeel. > > > On Sat, May 3, 2008 at 5:00 AM, Samisa Abeysinghe <[EMAIL PROTECTED]> wrote: > > > For anyone who is interested: http://wso2.org/library/3532 > > > > Samisa... > > > > -- > > Samisa Abeysinghe Director, Engineering; WSO2 Inc. > > > > http://www.wso2.com/ - "The Open Source SOA Company" > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > >
