Hi all,
I'm wondering if I'm using the Neo4j graph database right. My current
graph structure contains many relations for every single node. Some of
the nodes have 1 relations which is hard to traverse using REST
server (collecting nodes is heavy on memory and transmitting is heavy on
Miklós,
you should actually do both :)
So go for the embedded version to create domain specific service calls for
interacting with your database.
And then expose those as your own REST-endpoints using either a Server-Plugin
or an unmanaged extension.
The current REST server API is too noisy
Thanks for the ideas!
OK, I'll tell a bit more about my current scenario. I use the graph to
store medium sized texts (various sizes, 1 - 30kb) with some properties,
their tokens (1-2-3 word phrases) with many properties, and some other
stuff too which is not relevant now.
Since I use the
Miklós,
perhaps there is some categorization you can do to the text nodes and introduce
intermediary nodes from the root node. (Or at least shard them by some number).
Then you could also do traversals from those intermediary nodes in parallel. If
that helps you too speed up.
What are you
A typical traversal while teaching is like this:
- grab 1 text node and all it's token nodes (can be cached in memory but
still need initial DB lookup)
- do calculations
- update token nodes.
There are usually 50-500 token nodes for a text node so 1 iteration in
teaching needs to access this
5 matches
Mail list logo
