Re: [basex-talk] BaseX xpath querying takes more time than SAX parser takes

Hi Elango I noticed, your code runs faster after you have corrected evaluated XPath, but anyway, one observation from my practice. In case, you need only one shot processing of the file, and your task fits for use of SAX parser, then the SAX parser will be the most efficient and the fastest. BaseX

Re: [basex-talk] BaseX xpath querying takes more time than SAX parser takes

…glad to hear it works. ___ > Thanks Christian for your response, > > I have done a mistake in my code. I have executed different xpaths against > both causes the time difference. Now I have executed same xpath against both > and BaseX xpath evaluation is faster than SAX. >

Re: [basex-talk] BaseX xpath querying takes more time than SAX parser takes

Hi Elango, to say anything on this, we probably need more information on how you are processing your data via SAX, and how you receive your result via session.query(expression).execute(). Do you have some self-contained code that allows us to get more insight into how you are testing? Best, Chris

[basex-talk] BaseX xpath querying takes more time than SAX parser takes

Hi All, I am trying to use BaseX Client and server with large XML files(13 MB size). I have created a database for the XML and evaluated an xpath in that. When I executed an xpath it takes around 250 milliseconds to fetch the results. In case of SAX parser I could get the response for the same xpa