纯粹在内存中运行 Neo4j,没有任何持久性 [英] Running Neo4j purely in memory without any persistence

查看:34
本文介绍了纯粹在内存中运行 Neo4j,没有任何持久性的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我不想保留任何数据,但仍想使用 Neo4j 来实现它的图遍历和算法功能.在嵌入式数据库中,我已经配置了 cache_type = strong 并且在所有写入之后我将事务设置为失败.但是我的写入速度(节点、关系创建速度)很慢,这正在成为我过程中的一大瓶颈.

I don't want to persist any data but still want to use Neo4j for it's graph traversal and algorithm capabilities. In an embedded database, I've configured cache_type = strong and after all the writes I set the transaction to failure. But my write speeds (node, relationship creation speeds) are a slow and this is becoming a big bottleneck in my process.

那么,问题是,Neo4j 是否可以在没有任何持久性方面而仅作为纯 API 运行?我尝试了 JGraphT 之类的其他方法,但它们没有 Neo4j 提供的遍历机制.

So, the question is, can Neo4j be run without any persistence aspects to it at all and just as a pure API? I tried others like JGraphT but those don't have traversal mechanisms like the ones Neo4j provides.

推荐答案

据我所知,Neo4J 数据存储和 Lucene 索引总是写入文件.至少在 Linux 上,您可以设置一个 ramfs 文件系统来将文件保存在内存中.

As far as I know, Neo4J data storage and Lucene indexes are always written to files. On Linux, at least, you could set up a ramfs filing system to hold the files in-memory.

另见:

这篇关于纯粹在内存中运行 Neo4j,没有任何持久性的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆