Andrew,
if you upgrade to 1.4.M06, your shell should be able to do Cypher in
order to count the relationships of a node, not returning them:

start n=(1) match (n)-[r]-(x) return count(r)

and try that several times to see if cold caches are initially slowing
down things.

or something along these lines. In the LS and Neoclipse the output and
visualization will be slow for that amount of data.

Cheers,

/peter neubauer

GTalk:      neubauer.peter
Skype       peter.neubauer
Phone       +46 704 106975
LinkedIn   http://www.linkedin.com/in/neubauer
Twitter      http://twitter.com/peterneubauer

http://www.neo4j.org               - Your high performance graph database.
http://startupbootcamp.org/    - Öresund - Innovation happens HERE.
http://www.thoughtmade.com - Scandinavia's coolest Bring-a-Thing party.



On Wed, Jul 6, 2011 at 4:15 PM, Andrew White <li...@andrewewhite.net> wrote:
> I have a graph with roughly 10M nodes. Some of these nodes are highly
> connected to other nodes. For example I may have a single node with 1M+
> relationships. A good analogy is a population that has a  "lives-in"
> relationship to a state. Now the problem...
>
> Both neoclipse or neo4j-shell are terribly slow when working with these
> nodes. In the shell I would expect a `cd <node-id>` to be very fast,
> much like selecting via a rowid in a standard DB. Instead, I usually see
> several seconds delay. Doing a `ls` takes so long that I usually have to
> just kill the process. In fact `ls` never outputs anything which is odd
> since I would expect it to "stream" the output as it found it. I have
> very similar performance issues with neoclipse.
>
> I am using Neo4j 1.3 embedded on Ubuntu 10.04 with 4GB of RAM.
> Disclaimer, I am new to Neo4j.
>
> Thanks,
> Andrew
> _______________________________________________
> Neo4j mailing list
> User@lists.neo4j.org
> https://lists.neo4j.org/mailman/listinfo/user
>
_______________________________________________
Neo4j mailing list
User@lists.neo4j.org
https://lists.neo4j.org/mailman/listinfo/user

Reply via email to