You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@clerezza.apache.org by "Reto Bachmann-Gmür (JIRA)" <ji...@apache.org> on 2010/07/05 16:31:51 UTC

[jira] Closed: (CLEREZZA-194) Replace the integrated SPARQL engine

     [ https://issues.apache.org/jira/browse/CLEREZZA-194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Reto Bachmann-Gmür closed CLEREZZA-194.
---------------------------------------

      Assignee: Reto Bachmann-Gmür
    Resolution: Won't Fix

While a Fastlane might improve perfoamce, no sparql engine is known that is likely to be faster than arq

> Replace the integrated SPARQL engine
> ------------------------------------
>
>                 Key: CLEREZZA-194
>                 URL: https://issues.apache.org/jira/browse/CLEREZZA-194
>             Project: Clerezza
>          Issue Type: Improvement
>            Reporter: Oliver Strässer
>            Assignee: Reto Bachmann-Gmür
>            Priority: Critical
>
> The Scalability of the integrated SPARQL engine isn't very good.  Some test with big graphs demonstrate this problem. 
> A Query over a big Graph (120 MB) needs more than 45 seconds with SPARQL. The same "query" build with graph.filter(triple) calls, needs only 1-2 msec - quite faster. 
> research with Manuel Innerhofer shows, that the problem is the hasnext() method of the SPARQL  resultset.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.