[redland-dev] Triple storage overhead

[Sébastien Pierre]

Hello,

Morten Frederiksen wrote:

>On Friday 28 May 2004 18:35, Sébastien Pierre wrote:
>  
>
>>I am a Redland newbie and use it through the Python interface. I am
>>currently using Redland BDB storage as a backend for a software
>>configuration management system I am working on.
>>I was surprised to see that storing triples composed roughly of 2 40
>>chars strings for subject and object, plus a 10 chars predicate would
>>consume 3 to 6 times the total size of these strings on the disk.
>>    
>>
>This does sound like a classic case of a data model in need of normalisation.
>  
>
What do you precisely call "normalisation" ?

>If you store a large number of triples, you might want to have a look at the 
>MySQL storage engine now provided with Redland (I wrote it), it is highly 
>normalised, so at least storage wise it should be more efficient.
>  
>
I may store between 10 000 and 100 000 triples, so your MySQL storage 
seems interesting. However, I would like to know if it is possible to 
migrate a storage from the BDB backend to your MySQL backend ? This 
would be interesting as I don't want to force people to install MwSQL to 
use my software.

TIA,

 -- Sébastien