On Wed, Feb 10, 2010 at 2:35 PM, Dmitri Livotov wrote:
> Thanks for all your detailed responses. We now moved forward for stress
> testing it initial results shows a quite well performace, we're now
> running random reads, traversing and updates from 100 parallel threads
> and average response on
t;
>>>>
>>>>
>>> An interesting approach Rick,
>>>
>>> However I'd go for something simpler to avoid those millions of
>>> relationships that would go to that one node as you said. I'd only
>>> have the "top"
that one node as you said. I'd only
>> have the "top" (root) folders be connected to that node and then
>> traverse the tree when you'd like to find the files/folders. The cost
>> for traversing both (filtered) folders and files is quite low and
>> you'd get r
that one node as you said. I'd only
>> have the "top" (root) folders be connected to that node and then
>> traverse the tree when you'd like to find the files/folders. The cost
>> for traversing both (filtered) folders and files is quite low and
>> you'd get r
the tree when you'd like to find the files/folders. The cost
> for traversing both (filtered) folders and files is quite low and
> you'd get rid of that "heavy" node with loads of relationships on it.
>
> In fact, I've created some layouts like that and it worked fi
7;d get rid of that "heavy" node with loads of relationships on it.
In fact, I've created some layouts like that and it worked fine with
several millions files/folders at least.
>
> -Original Message-----
> From: user-boun...@lists.neo4j.org [mailto:user-boun...@lists.neo4
ene as well.
Hope this helps.
Rick
-Original Message-
From: user-boun...@lists.neo4j.org [mailto:user-boun...@lists.neo4j.org] On
Behalf Of Dmitri Livotov
Sent: Monday, February 08, 2010 8:26 AM
To: Neo user discussions
Subject: [Neo] Node with the millions of incoming relationships "to&qu
A kind of architectural question now
We're thinking on our graph model now, where we will have a lot of nodes
of particular type. Something like the filesystem, where each fs element
(node in neo4j terms) could be of type "file" or "folder".
We need to be able to separate and later query (f
8 matches
Mail list logo