Sorry for the late reply We identified a problem with a similar old fuseki version. Using the internal backup mechanism caused fuseki to slow down drastically and take down our website, usually ending in us restarting.
We disabled the fuseki internal backups and instead make Linux lvm snapshots of the database and back it up via tdbdump. We restart fuseki as part of the process to ensure a consistent database. That’s fast enough that we just live with the outage. Sent from Phone, apologies for typos and/or brevity On Thu, Sep 5, 2024 at 8:08 AM Hugo Mills <hugo.mi...@agrimetrics.co.uk> wrote: > Hi, all, > > > > We’ve got a heavily-used webapp backed by Fuseki, and we’re having issues > with the load on the Fuseki server. It frequently heads into a storm of > high load average, with the CPU usage pegged at 600% (on 6 cores), and then > the app grinds to a halt and we have to restart the database. We’re trying > to understand why this is happening. Is there the ability in Fuseki to get > a list of the currently-running queries at any given point in time, > including the query text itself, and preferably also the amount of time > each one has been running for? > > > > We’re running Fuseki from Jena 3.4.0, if that makes a difference to the > answer. > > > > Thanks, > > Hugo. > > > Hugo Mills > Development Team Leader > agrimetrics.co.uk <https://www.agrimetrics.co.uk/> > Reading Enterprise Centre, Whiteknights Road, Reading, UK, RG6 6BU > <https://www.linkedin.com/company/agrimetrics/> > <https://x.com/agrimetrics?s=21&t=h8BsEr4MroKUB8051AMAdA> >