If I understand, you have an 80MB collection. Even if xindice were reading this 1 disk block at a time to scan the entire collection in some dumb fashion, it should be faster than 256s. Notice that the cpu time is only about 3s, so all the delay is in some kind of i/o or paging -- something involving how the operating system is configured, probably. Sorry to be of so little help.
Jeff ----- Original Message ----- From: "Matthew Van Horn" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Sunday, November 10, 2002 10:33 PM Subject: Re: Performance question (Am I doing something wrong?) > Contrary to what you might think, Jeff, the performance actually > degrades a bit when I am explicit: > (By the way, "candidate" is the root element and there is only one > document with this ID) > > % /usr/bin/time xindice xpath -c /db/resumes -q > "/candidate[biographic_data/id='ANON2021']" > ANON2021_2.xml > 372.72 real 2.22 user 1.22 sys > % /usr/bin/time xindice xpath -c /db/resumes -q > "//candidate[biographic_data/id='ANON2021']" > ANON2021_2.xml > 334.25 real 2.28 user 1.09 sys > > I think the above times are both substantially slower because this > time I had JBuilder running at the same time. > > When I shut down JBuilder, I got the following, which still shows the > "//candidate" is faster than "/candidate" > > % /usr/bin/time xindice xpath -c /db/resumes -q > "/candidate[biographic_data/id='ANON2021']" > ANON2021_2.xml > 256.52 real 2.10 user 1.12 sys > % /usr/bin/time xindice xpath -c /db/resumes -q > "//candidate[biographic_data/id='ANON2021']" > ANON2021_2.xml > 171.18 real 1.92 user 0.87 sys > > Maybe Xindice is optimized for //element searching someow?
