It turns out that the performance degradation was caused by a flaw in my application logic which was felt more acutely with the Sleepycat store.
Looking at the timing results, it seems like leaving the connection open is the way to go. Thanks. On Thursday, December 28, 2017 at 12:14:57 PM UTC-6, scossu wrote: > > Hello, > I am writing a Flask app that uses RDFLib to interact with a back end RDF > store. I am testing with two different setups, one using the > SPARQLUpdateStore connector and one using the Sleepycat one. > > At the moment I am initiating the store connection in the Flask app > initialization phase; which means that the connection stays open across > requests, as long as the application is not restarted. > > with the SPARQL/HTTP connector this seems to have no negative effect; with > the Sleepycat connector performance degrades visibly after each request. I > don't notice that with the SPARQL connector. > > If I open and close the Sleepycat connection with each request, even a > very simple operation operation on a small database takes more than 1 > second. > > I have two questions: 1) Is it best to open and close the Sleepycat > connector after each request, or leave it open? And 2) Shall I use > different strategies if I want to use the Sleepycat and SPARQL connectors > interchangeably? > > Thanks. > -- http://github.com/RDFLib --- You received this message because you are subscribed to the Google Groups "rdflib-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/rdflib-dev/f38309e2-0fb8-4b26-848c-d473810757f9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
