Coincidentally, I just tried this out earlier today. `pageRank` yielded a stack overflow, and `pageRank.stream` yielded an OOM error. The graph it was run on was large, but not unreasonably so. Haven't dug into the cause of the errors yet.
This is likely a query issue; I've had many queries go wild & OOM, once fixed they work as you'd expect. There's also a config setting you can use to limit in seconds the amount of time a query can run before it's killed, very useful if you plan on running hand built queries on anything production (which you shouldn't be anyways ;-))
Can you share more info about the queries that "went wild" on GitHub, so that we can reproduce? Thx
Would love to know more. Can you raise an issue with more details on GitHub please?
Neo4j is awesome, after using at my last startup I'm super meh on table based schemas.
Does the pagerank algorithm include the personalized variant? The docs don't seem to indicate that this is the case (i.e. no way to specify an alpha vector).