Yeah, that'll blow up building the result set I reckon. You don't need to return the data to get neo to cache it, you just need a query that will touch all data in the database. Something like this:
MATCH (n)-[r]->() WHERE n.propertyThatDoesNotExist = 12 RETURN count(*) Still, I'm not sure there's a reason you'd want to do this - you may be better served just running the queries you actually wanna run against the dataset. It'll be a bit slower the first time the query runs, but then the data will be cached. /jake On Sat, Mar 22, 2014 at 1:35 AM, Alx <[email protected]> wrote: > I have plenty of RAM on my computer and I would like to load the whole > graph db on the memory for faster querying. So far I have added "cache_type > = strong" in the 'neo4.properties' file. > > How is it possible to run a cypher query to traverse through all the > nodes? I ran a simple query with a limit of 500K nodes on the data browser > and it gave me an error: "OutOfMemoryError Java heap space" > > -- > 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.
