incubator-clerezza-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Reto Bachmann-Gmür (JIRA) <j...@apache.org>
Subject [jira] Commented: (CLEREZZA-286) Inserting lager literals takes too long
Date Mon, 06 Sep 2010 14:36:32 GMT

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

Reto Bachmann-Gmür commented on CLEREZZA-286:
---------------------------------------------

Hi Manuel, could you indicate steps to reproduce the described problems?

To your question "how will I create a MGraph that shouldn't externalize its literals?" That's
not currently possible (apart from the hacks you describe), but I think this is a more general
issue, there is no support to somehow constrain the TcProvider chosen, triple collcetions
are always created ba the one with the highest priority. It might be desirable to be able
to tell the TcManager what the requirement are and that the best provider for that purpose
is chosen (criteria might be read-performance, write-performance, size, leanification, ...).

> 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