> The biggest win of using a full path instead of // in Mark > Logic is that once the fragment is fetched, it allows the > server to more quickly find the desired node within the > fragment. With // the server has to walk the whole fragment > tree while with a direct path it can go straight to the right node. > > With xdmp:estimate(), things can actually be faster by using > // because that reduces the number of term lists that have to > be intersected, and since you're not fetching fragments the > advantage listed above doesn't apply.
I guess this is because xdmp:estimate is only looking at fragments. So you might say that one should use // to navigate to fragment roots, and use full paths to navigate within fragments. But that would requires putting knowledge of fragmentation into your code, which won't make things more flexible.. Kind regards, Geert Drs. G.P.H. Josten Consultant http://www.daidalos.nl/ Daidalos BV Source of Innovation Hoekeindsehof 1-4 2665 JZ Bleiswijk Tel.: +31 (0) 10 850 1200 Fax: +31 (0) 10 850 1199 http://www.daidalos.nl/ KvK 27164984 De informatie - verzonden in of met dit emailbericht - is afkomstig van Daidalos BV en is uitsluitend bestemd voor de geadresseerde. Indien u dit bericht onbedoeld hebt ontvangen, verzoeken wij u het te verwijderen. Aan dit bericht kunnen geen rechten worden ontleend. _______________________________________________ General mailing list [email protected] http://xqzone.com/mailman/listinfo/general
