Hi Andrey,

I use the latest development release downloaded from orientechnologies.

What you mean with "embedded in vertex"? I tried it with lightweight edges 
and also with edges stored as separate records. Always the same slow result.

When i use projection like "select @rid from #13:12345" then the respond 
lasts 0.002 seconds. 

Thank you



Am Dienstag, 2. Dezember 2014 07:48:21 UTC+1 schrieb Andrey Lomakin:
>
> Hi Mark.
> In non-distributed database you should not have any problems with your 
> case, but that is not true (yet) for distributed database .
> Could you answer on my previous question do you use distributed database ?
> On Dec 2, 2014 2:17 AM, "Mark H." <[email protected] <javascript:>> 
> wrote:
>
>> Hi Andrey,
>>
>> Could you please expand your explanation on "edges are all embedded in 
>> vertex instead and not stored in separate data structure"?
>>
>> I had a design question posted in 
>> https://groups.google.com/forum/#!topic/orient-database/0Wvk5dR1WBo on 
>> whether or not it's a bad design/practice to have vertices where edges in 
>> between them will grow indefinitely as time passes. I actually have sample 
>> vertex and edge classes posted in the mentioned link. 
>> Could you also please provide feedback whether the design I mentioned is 
>> bad and if there's better way to model it?
>>
>> Thank you.
>>
>> On Monday, December 1, 2014 2:37:47 AM UTC-5, Andrey Lomakin wrote:
>>
>>> HI,
>>> Do you use distributed version of orientdb ?
>>>
>>> I believe that your edges are all embedded in vertex instead and not 
>>> stored in separate data structure.
>>>
>>> On Fri, Nov 28, 2014 at 11:03 PM, Mario <[email protected]> 
>>> wrote:
>>>
>>>>
>>>> Hi everybody,
>>>>
>>>> I have a question on Vertex with many edges.
>>>> would be glad if someone could tell me why it´s so slow.
>>>>
>>>> Ok, thats the facts.
>>>>
>>>> Vertex Object  #13:12345 with 40.000 in_Participant, 160.000 
>>>> in_Receiver and 30.000 out_Sender
>>>>
>>>> When i select this Object like "select from #13:12345" it takes about 
>>>> 25 seconds to get the result.
>>>> Why is it that slow? And why has the amount of edges that effect?
>>>>
>>>> I tried it on orientdb-community-2.0-M2 and orientdb-community-2.0-M3
>>>>
>>>>
>>>>
>>>> Thanks a lot
>>>> Mario
>>>>
>>>>  
>>>>
>>>>
>>>>  -- 
>>>>
>>>> --- 
>>>> 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/d/optout.
>>>>
>>>
>>>
>>>
>>> -- 
>>> Best regards,
>>> Andrey Lomakin.
>>>
>>>   -- 
>>
>> --- 
>> 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] <javascript:>.
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 

--- 
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/d/optout.

Reply via email to