You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Martin Pekár (Jira)" <ji...@apache.org> on 2022/01/07 09:27:00 UTC

[jira] [Comment Edited] (JENA-2228) Does Fuseki2 use TDB indexes or indexes for in-memory store?

    [ https://issues.apache.org/jira/browse/JENA-2228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17470467#comment-17470467 ] 

Martin Pekár edited comment on JENA-2228 at 1/7/22, 9:26 AM:
-------------------------------------------------------------

I have added the existence check in TupleTable, which is accessed by the _nodeTupleTable.find()_ ** call. I assume, when all it is true that _!NodeId.isAny(_
_)_ for all NodeIds in the tuple, then the corresponding triple is fully concrete. Is this true?

I am running a benchmark with this new code, at it seems to work.


was (Author: mrpekar):
I have added the existence check in TupleTable, which is accessed by the _nodeTupleTable.find()_ ** call. I assume, when all it is true that _!NodeId.isAny()_ for all NodeIds in the tuple, then the corresponding triple is fully concrete. Is this true?

I am running a benchmark with this new code, at it seems to work.

> Does Fuseki2 use TDB indexes or indexes for in-memory store?
> ------------------------------------------------------------
>
>                 Key: JENA-2228
>                 URL: https://issues.apache.org/jira/browse/JENA-2228
>             Project: Apache Jena
>          Issue Type: Question
>          Components: Fuseki, TDB
>    Affects Versions: Jena 3.17.0
>         Environment: I am running the jena-fuseki-server-3.17.0.jar file from jena-fuseki2/jena-fuseki-server/target/ as follows
> {code:java}
> java -Xmx500g -jar fuseki-jenaclone.jar --tdb2 --loc=db/jena --timeout=1000000 /jena &{code}
>            Reporter: Martin Pekár
>            Priority: Major
>
> Based on logging messages inserted into various places in the indexes in the TDB module (NodeTupleTableConcrete, TupleIndexBase, NodeTableNative, BPlusTree), I can see that the B+ tree is only used once per query. I have inserted logging messages for every finding method to see which classes are used when querying. I would expect to the the B+ tree be used several times per query.
>  
> I use the error logging level, and I inserted logging in the class constructors to make sure logging worked. I see construction of all the index classes.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)