GitHub user afs added a comment to the discussion: Difference between tdb2.tdbupdater and update endpoint
Hi @decdocuteam, I don't see any particular area that wouldd trigger the situation - may I ask for some more detail (below) so That I understand what's going on. > doing the update through the Fedora Camel toolbox I don't know that that way of making updates. For a test would you be able to send an update dirct to the Fuseki endpoint and see whether it takes a similar length of time? > What is the difference between tdb2.tdbupdate and the update endpoint? If you have a tdb2.tdbupdate***r*** or tdb2.tdbupload then these is not from Jena - are they local customizations? `tdbupdate` runs an update and should refuse to run if Fuseki is using the database. If `tdbupdate` is running wen Fuseki is (1) its not the same database, e.g. if it is a different `Data-` directory, or is in the top level TDB directory, or (2) maybe you have a container setup where the filesystem is mapped in which case two OS's are trying to manage the same DB - Jena tries to catch this but there are many ways to configure a container, and we may not be able to lock in all cases. What is the storage configuration for the server? SSD? Disk? Virtualized remote disk? Other than that, a SPARQL Update should be the same. What does an update look like? Presumably the update is no using the Graph Store Protocol which can be used to send (i.e add) data. What is the load on the server? While queries and updates are isolated and one update can happen in true parallel with queries, a heavy query load might affect the update. Are updates made one at a time or are there many over lapping updates, all small? GitHub link: https://github.com/apache/jena/discussions/3684#discussioncomment-15476107 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
