A sample environment
The following is the breakdown of a demo environment used for NodeGraph:
| Data assets and queries |
Total |
|---|---|
| QVWs | 10 |
| QVFs | 0 |
| QVDs | 188 |
| Model tables | 302 |
| Fields | 4939 |
| Inline loads | 6 |
| Queries | 190 |
| Data assets and queries |
Total |
|---|---|
| Total nodes | 9730 |
| Total links | 20185 |
NodeGraph uses a graphDB on disk of 53 MB. It is stored uncompressed on disk but compressed when in NodeGraph memory.
However, NodeGraph compensates the compressing with an indexing storage and some cache of other things, plus the software overhead (although in any bigger environment the overhead should be of no relative size).
As a rough guideline, NodeGraph uses approximately [500 bytes * “size of the environment”] in terms of memory.
The CPU load is fairly large when processing the logs, but most CPU usage is consumed on the client side, with only delta requests from the client to the server, making no large footprint on the network. There is no real load on disk either, as most is written in a short time-frame during sync.