Good to know. 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.
Is this behavior something I can adjust with configuration or is it unavoidable? I see it on my mac as well so I don’t think it’s specific to the server configuration. I should also mention that I understand these kinds of questions would normally be addressed through a consulting engagement with the BaseX team—I would definitely pursue that but at the moment time is of the essence as this use of BaseX was completely unplanned but suddenly very much desired… Thanks, Eliot _____________________________________________ Eliot Kimber Sr Staff Content Engineer O: 512 554 9368 M: 512 554 9368 servicenow.com<https://www.servicenow.com> LinkedIn<https://www.linkedin.com/company/servicenow> | Twitter<https://twitter.com/servicenow> | YouTube<https://www.youtube.com/user/servicenowinc> | Facebook<https://www.facebook.com/servicenow> From: Christian Grün <[email protected]> Date: Monday, February 7, 2022 at 8:19 AM To: Eliot Kimber <[email protected]> Cc: [email protected] <[email protected]> Subject: Re: [basex-talk] Managing/Debugging Server Load and Performance [External Email] > I take it as a given that BaseX, properly configured and using queries that > are not poorly implemented should perform acceptably as a concurrent web > server with not too much load (10s or 100s of users, not 1000s of users). Absolutely. Our usual benchmark for commercial applications is to ensure that 90% (or more) of the queries take less than a second, and to only allow non-blocking queries to take more than 5 seconds.
