Sorry to say that but 5000 properties per node sound really a bit off, usually you would destructure that huge bag of information into a small subgraph of related nodes.
Usually in a graph model people have 5-20 properties in extreme cases perhaps 50. What is your model for / what does it look like? Michael On Sat, Dec 10, 2016 at 4:53 PM, Eric Mumford <[email protected]> wrote: > I have an application that takes in about 20 nodes of data per day, each > with about 5000 properties. > > I am finding that creating nodes with on the order of ~5000 properties > renders the database inoperable on my MacBook Pro. > > Is my schema horrible? Should I restructure so Neo4j can manage it better? > > What are the reasonable limits to number of properties and nodes on a > desktop instance? At what capacity point should I move my system to a cloud > installation, and what experimental evidence is available demonstrating > that scale quantity? > > Thank you, > Eric > > -- > You received this message because you are subscribed to the Google Groups > "Neo4j" 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. > -- You received this message because you are subscribed to the Google Groups "Neo4j" 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.
