Hi James
Reducing the problem space means the following xquery - run in basexgui 8.5
- has gone from an average of 148000ms to 3900ms:
…sounds good. And thanks for the details.
However, doesn't this show an issue in how BaseX maintains it's indexes?
BaseX has no inverted indexes for element and attribute nodes (see [1] for more information on our index structures). In most applications, this works pretty well, because we’ve spent a lot of effort in speeding up sequential access to document structures, but for 40 GB, too much data temporarily moved to main-memory.
Hope this helps Christian