incubator-clerezza-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hasan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CLEREZZA-286) Inserting lager literals takes too long
Date Wed, 25 Aug 2010 12:37:16 GMT

    [ https://issues.apache.org/jira/browse/CLEREZZA-286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12902407#action_12902407
] 

Hasan commented on CLEREZZA-286:
--------------------------------

I don't quite get your description. 
If I want to create an MGraph http://mygraph without externalization of base64 literals then
I will call TcManager.createMGraph("http://mygraph")
and since LiteralExternalizingProvider has a higher weight, it will be invoked by TcManager.
But then what will it do actually?
- Calling TcManager with an extended graphName
or
- Throwing Unsupported erxception since the graphName does not end with "-externalizedliterals"

Assuming it calls TcManager with an extended graphName, then what will TcManager do? Iterating
again through the provider list? and calling again LiteralExternalizingProvider?

Another alternative:
If we don't "misuse" the graphname parameter in createMGraph, we may need to provide a second
signature for creaeteMGraph which takes a second parameter for specifying externalization
of base64 literals. But then we have to change every implementation of TcProvider to implement
this method or we change TcProvider from interface to an abstract class. 
What are other consequences here?


> Inserting lager literals takes too long
> ---------------------------------------
>
>                 Key: CLEREZZA-286
>                 URL: https://issues.apache.org/jira/browse/CLEREZZA-286
>             Project: Clerezza
>          Issue Type: Improvement
>            Reporter: Reto Bachmann-Gmür
>            Assignee: Reto Bachmann-Gmür
>
> As binary resources are stored as literal values in the graph inserting literals of many
MB is not a seldom usage scenario. Inserting such literals however take very long and thus
require a very long write-lock on the graph (e.g. on my laptop 9 seconds when uploading a
40MB file with TDB and 3 second with Sesame)

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


Mime
View raw message