First of all, arrays are evil.
:(
-V
On Thu, Jun 26, 2008 at 4:13 PM, Peter Haensgen <[EMAIL PROTECTED]>
wrote:
> Hi,
>
> a reason for performance problems might be the way that the information
> about nodes and relationships are collected by the graph viewer.
>
> Currently, we implement the interface
> "IGraphEntityRelationshipContentProvider" from Zest which defines a
> method "Object[] getRelationships(Object source, Object dest)".
>
> I believe (haven't checked the Zest source code) that in order to
> determine all relationships between all displayed nodes this method will
> be invoked n^2 times, e.g.
>
> for (all displayed nodes as source)
> {
> for (all displayed nodes as target)
> {
> Object[] rels = contentProvider.getRelationships(source,
> target);
> ... do something ...
> }
> }
>
> So maybe there is another way to tell Zest about the existing nodes and
> relationships?
>
> regards,
> Peter
>
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]
> > On Behalf Of Anders Nawroth
> > Sent: Donnerstag, 26. Juni 2008 12:32
> > To: User@lists.neo4j.org
> > Subject: [Neo] neoclipse performance
> >
> > hi!
> >
> > I tested Neoclipse with some bigger node spaces.
> >
> > The attached image shows 215 nodes and 807 relationships. It takes 3
> > seconds to render on my laptop. (the full nodespace is 250/1000
> > nodes/rels in this case)
> >
> > I'd say:
> > * too slow to be useful
> > * the graph UI doesn't fit this kind of inspections
> >
> > The use I can see for now is to browse the nodespace with a rather low
> > traversal depth. This also performs well.
> >
> > To render bigger graphs, some other kind of UI would be needed.
> >
> >
> > /anders
>
> _______________________________________________
> Neo mailing list
> User@lists.neo4j.org
> https://lists.neo4j.org/mailman/listinfo/user
>
--
Viktor Klang
Rogue Software Architect
_______________________________________________
Neo mailing list
User@lists.neo4j.org
https://lists.neo4j.org/mailman/listinfo/user
