Well. That’s why I said I’ll have another look at this. Feel free to send us a link to your data, this might simplify the analysis.
I have done some tests with larger databases (with up to 1 mio documents), and I have found a way to speed up the directory traversal via WebDAV. It MAY also affect the targeted retrieval of single resources. A new snapshot is available [1]. I’d appreciate if you could give me some feedback on the questions in my last mail; this might help us to help you (I’m still not sure which operations in your database instance are slow and which are fast, as I couldn’t reproduce this on my test database instances).
@everyone: The new convenience function db:dir was added [1]. It is utilized by our WebDAV implementation, and it can be used to list all resources and sub folders of a database directory. Database directories in BaseX are all virtual: They implicitly result from the paths of stored resources.
Cheers, Christian
[1] http://files.basex.org/releases/latest/ [2] http://docs.basex.org/wiki/Database_Module#db:dir
On Thu, Jan 10, 2019 at 7:19 AM Christian Grün christian.gruen@gmail.com wrote:
See my first mail…also requests to other arbitrary documents are slow (in the range of course 700ms and higher).
Well. That’s why I said I’ll have another look at this. Feel free to send us a link to your data, this might simplify the analysis.
We did not choose a vendor specific API because we want to have data portability and a unified API.
Sounds completely reasonable.
Please note that developers regularly experience a lot of surprises and challenges when switching from one vendor to another, as XML databases have much more idiosyncrasies than relational databases (performance of APIs is just one of them). We try to minimize the challenge (e.g. by developing joint EXPath and EXQuery modules with other vendors), but of course this is often difficult if vendors have already chosen a specific solution.
Would you like to share your experiences with MarkLogic and WebDAV with us?