I'm looking for a solid open-source graph database that does *not* need to scale (and thus is relatively easy to set up and maintain).
Is neo4j a good choice, or are there other databases I should consider?
Ask HN: What Is Going on with Neo4j? | Hacker News
Ask HN: What Is Going on with Neo4j? | Hacker News
Ask HN: What Is Going on with Neo4j? | Hacker News
I will say #neo4j is one of the fastest moving large software projects I've ever used. Every day you log in and there's a TON more stuff. This is both good and difficult!
Obsidian & Neo4j & graph analyses
hmmm maybe spacing them out doesn't make sense because then there'd be more jobs to cleanup per run so they might still overlap. increasing batch size may speed it up but am still concerned with memory usage.
okay, maybe try apoc.periodic.commit first, that way, we can also isolate the effect.
gotta take a look at these on Monday:
1. check for overlap by job's time taken
2. space out recurring cleanup jobs to prevent overlap
3. use apoc.periodic.commit to prevent pre-loading nodes outside of the batch to memory?
re #2, two weeks ago, we found a bug that kept around some jobs that should've been cleaned up from our Neo4J jobs database. it was brought to light when our db kept crashing with OOM. it stopped crashing when we disabled the cleanup jobs.
the thing is, we're already using apoc.periodic.iterate to batch the detach deletes. however, the cleanup was scheduled hourly.
i'm not sure whether a single run was enough to cause the OOM, or it was overloading because of overlap.
new learnings today!
1. passing null to Elasticsearch filter is basically a match_all
2. looked into high volume transactions in neo4j by apoc periodic executions