Hi! I'm Martin, I'm a software developer new to the Triples/SPARQL world. I'm currently building queries against a Fuseki/TDB backend (that I can work on too) and I'm getting into significant performance problems (including never ending queries). Despite what I thought was a good search on the apache jena website I could not find a lot of insight about performance investigation so I'm trying it here.
Most of my data experience comes from the relational world (ex: PG) so I'm sometimes drawing comparisons there. To give some context my data set is around 15 linked concepts, with the number of triples for each ranging from some hundreds to 500K - total less than 2 millions (documents/authors/publication kind of data). Unto questions: - When I'm facing a slow query, what are my investigation options. Is there an equivalent of an "explain plan" in SQL pointing to the query specific slow points? What's the advised way for performance checks in SPARQL? - Are there any performance setups to be aware of on the server side? Like ways to check indexes are correctly built (outside of text search that I'm not working with for the moment) - We're currently using TDB1. I've seen the transactional benefits of TDB2 - are there performance improvements too that would warrant a migration there ? Thanks a lot already! Martin -- *Martin Van Aken - **Freelance Enthusiast Developer* Mobile : +32 486 899 652 Follow me on Twitter : @martinvanaken <http://twitter.com/martinvanaken> Call me on Skype : vanakenm Hang out with me : mar...@joyouscoding.com Contact me on LinkedIn : http://www.linkedin.com/in/martinvanaken Company website : www.joyouscoding.com
