Thanks Andrey. One comment. Currently ridBag is base64 encoded. It adds an 
additional overhead and relatively simple document starts to be heavy.
For instance previously I had document (130 bytes)

#42:0 v12 
DbPedResource@out_DbPedLinks:<#43:2,#43:3,#43:4,#43:5,#43:6,#43:7,#43:8,#43:9,#43:10,#43:11,#43:12>,Uri:"AWK",Related:[]

now after change (218 bytes)

#42:0 v12 DbPedResource@out_DbPedLinks:%
AQAAAAsAKgAAAAAAAAABACoAAAAAAAAAAgAqAAAAAAAAAAMAKgAAAAAAAAAEACoAAAAAAAAABQAqAAAAAAAAAAYAKgAAAAAAAAAHACoAAAAAAAAACAAqAAAAAAAAAAkAKgAAAAAAAAAKACoAAAAAAAAACw==
;,Uri:"AWK",Related:[]

The EmbeddedRidBag itself is space consuming due to 8bytes indexes for even 
small numbers. Base64 makes it even worse.
Generally , my sugestion is to reconsider BSON like format 
http://bsonspec.org
which should eliminate that problem and improve performance.
WDYT?

Pawel


On Thursday, February 6, 2014 10:06:40 PM UTC+1, Andrey Lomakin wrote:
>
>
> On Thu, Feb 6, 2014 at 11:04 PM, Pawel K. <[email protected] 
> <javascript:>>wrote:
>
>> And when can I expect to get embedded not a tree form in document via 
>> binary protocol?
>>
>
> If amount of items more than ridBag.embeddedToSbtreeBonsaiThreshold which 
> is 80 now.
>
>
>
> -- 
> Best regards,
> Andrey Lomakin.
>
> Orient Technologies
> the Company behind OrientDB
>
>  

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to