Re: huge fuseki memory usage; NIO errors; heap NOT running out

Will do, thanks. Rob Vesse June 15, 2018 at 6:19 AM Dan Is there any chance you could try grabbing a JVM thread dump next time you notice this happening? There are multiple ways to do this depending on your environment, the simplest and most portable is just

Re: Fuseki errors with concurrent requests

Hi, unfortunately I haven't been able to make a standalone package yet. However with jena 3.7.0 things are bit better now - errors occur less than before. Actually now I'm not getting error codes from Fuseki (all 200), but errors still occur and at that time there is Fuseki output  

Re: Long response times on TDB queries

Ok, did the output show that the stats.opt file was actually being used? Note the file has to be named exactly that and be placed in the database directory You can modify the generated file to tweak the optimiser behaviour if you still don't get good reorderings even with the statistics, the

Re: Long response times on TDB queries

Rob, I had actually generated the statistics file prior to getting in touch. I meant to attach it to the original message, but it was too large, the message wouldn't send. It, however, didn't seem to make a large dent in the time the query took to execute. Adam

Re: Long response times on TDB queries

Adam Did you try generating the statistics file as well? Doing that should allow TDB to more intelligently reorder triple pattern execution within BGPs and hopefully avoid the need to manually adjust queries Rob On 15/06/2018, 13:13, "Adam Ladly" wrote: Hi Rob, Just tried

Re: Long response times on TDB queries

Hi Rob, Just tried re-ordering it as you suggested, and this was exactly the improvement that I needed. Now getting returns in 0.1 seconds rather than 200+. Much appreciated, Adam From: Rob Vesse Sent: 15 June 2018 12:12 To: users@jena.apache.org Subject:

Re: Long response times on TDB queries

On 15/06/2018, 11:46, "Adam Ladly" wrote: 22:18:21 INFO exec :: Reorder/generic ?node ?id ?node ?p "http://www.ncbi.nlm.nih.gov/gene/1956; So it looks like TDB is using a generic execution ordering and for your data this is clearly

Long response times on TDB queries

Hi, I am creating a tdb dataset using the uniprot files available over their public ftp servers. The goal of this is to map between 2 different Ids. The TDB store has been created, but I'm experiencing some slow query speeds, and was wondering if there's anything I'm missing that could improve

Re: huge fuseki memory usage; NIO errors; heap NOT running out

Dan Is there any chance you could try grabbing a JVM thread dump next time you notice this happening? There are multiple ways to do this depending on your environment, the simplest and most portable is just to send a SIGQUIT to the JVM process which will cause a thread dump to be output to