…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.

Regards, Elango.

On Fri, Feb 22, 2013 at 3:51 PM, Christian Grün <christian.gruen@gmail.com> wrote:

...

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, Christian

On Wed, Feb 20, 2013 at 11:56 AM, elangovan MuthuSwamy <elangovan.h@gmail.com> wrote:

...

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 xpath within 5 seconds.

I used following BaseXClient code for this.

BaseXClient session = new BaseXClient("localhost", 1984, "admin", "admin");

// code to fetch the large XML file size. Read from the file. String xmlString = .......

InputStream bais = new ByteArrayInputStream(xmlString.getBytes()); session.create("database", bais);

String expression = "/configuration/protocol[starts-with(name, 'http')]/name";

session.query(expression).execute(); // this line takes 250 milliseconds to give the result. Where as same xpath can be executed within 5 milliseconds in SAX parser.

Am I basically missing anything or something else.

Please advice me.

Thanks in advance.

-- Regards, Elango.

-- Regards, Elango.