Re: [basex-talk] Managing/Debugging Server Load and Performance

I am seeing that when BaseX is doing some long-running process (constructing one of our big custom indexes) that it seems to consume all the BaseX cycles and the HTTP server becomes unresponsive.

If you perform expensive write operations on databases that other users want to access, they’ll need to wait until this operation is finished.

There are various ways out: You can e.g. create temporary instances of your index databases and drop the operative database instances after your maintenance operations have finished. For high-availability use cases, you can also work with multiple BaseX instances.

[…] this use of BaseX was completely unplanned but suddenly very much desired…

Always good to hear!