GrapheneDB Blog

Updates from the GrapheneDB team

Storage Tracking at GrapheneDB

We’re happy to announce that we’ve improved visibility on how data is distributed in disk so that you can have more control over your deployment.

The size that your deployment takes in the disk is important as there is a limit for your plan that you want to avoid hitting (read-only mode). Also having a good visibility on your dataset size will help you to for instance how much of your dataset fits into page cache and avoid hitting disk for reads, which is slower.

As of today there is a new section in the Overview page of your database showing the following info:


  • Databases: The size that your system db and your data databases takes in the disk. It also contains transaction files.
  • Nodes, Properties & Relationships: The size in disk for your property graph model will help you understand how the data is distributed within your graph
  • Indexes: Indexes are very important, but they come at a cost of write performance and disk size.
  • Extensions: This is the size in disk of your extensions.
  • Other: Other size in disk, like debug logs.

Prometheus endpoint All these storage metrics are also available via the Prometheus endpoint (see Insights tab) for your convenience in case you want to fetch them and create your own charts or alerts.

Email notifications We are sending now 2 warning emails at 85% and 95% before your deployment reaches the allowed disk size for your plan. We encourage you to upgrade your plan (you can do it now in-place) to avoid your database being put in read-only mode.

Moving forward We’re going to keep working in the next months on improving the visibility in the server. Please stay tuned!