Skip to content

Flexible storage #653

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 24 commits into
base: console
Choose a base branch
from
Open

Flexible storage #653

wants to merge 24 commits into from

Conversation

fiquick
Copy link
Collaborator

@fiquick fiquick commented Mar 25, 2025

No description provided.

Ideally, the database should all fit into memory (page cache) for the best performance.
Keep an eye on this metric to make sure you have enough storage for today and for future growth.
Keep an eye on this metric to make sure you have enough storage for future growth.
Copy link
Collaborator Author

@fiquick fiquick Mar 26, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well, the system should alert the user, right? I'm sure it does! Maybe they should be able to reset if from the Operations > Metrics > Resources > Storage - if that's where the graph is which tracks storage.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What graph are you referring to?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Storage graph
"Keep an eye on the storage graph to make sure you have enough storage for future growth.
The graph is available in Metrics > Resources > Storage."

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's a bit confusing to refer to this as a graph.

Copy link
Collaborator

@AlexicaWright AlexicaWright left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A few comments to consider.

There are two types of Aura instances:

* **AuraDB** (the default Aura instance type)
* **AuraDS** (the xref:graph-analytics/index.adoc#aura-ds[fully managed version] of Neo4j Graph Data Science)

Select the type of instance using the switch on the top right, then choose the plan that best suits your needs.
You can upgrade your plan later if your needs change.

///
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Two slashes is a comment, just FYI

@@ -49,6 +49,10 @@ See xref:managing-instances/custom-endpoints.adoc[Custom endpoints] for more inf
It runs on container technology and this allows for the AuraDB Instance to allocate dedicated CPU resources.

|Storage
|Neo4j Aura automates the backup process (you can also create your own on-demand snapshots), storing your data securely in the cloud. Backups are saved in the storage bucket of the cloud provider in the same region as your Neo4j Aura instance.

Storage is adjustable independent of memory for AuraDB pre-paid billing on Google Cloud Platform (GCP), version 5.x. See xref:/managing-instances/instance-actions/#_flexible_storage[Flexible storage] for more information.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Storage is adjustable independent of memory for AuraDB pre-paid billing on Google Cloud Platform (GCP), version 5.x. See xref:/managing-instances/instance-actions/#_flexible_storage[Flexible storage] for more information.
Options for flexible storage is available for AuraDB pre-paid billing on Google Cloud Platform (GCP), latest version.
See xref:managing-instances/instance-actions.adoc#_flexible_storage[Flexible storage] for more information.

|Neo4j Aura automates the backup process (you can also create your own on-demand snapshots), storing your data securely in the cloud. Backups are saved in the storage bucket of the cloud provider in the same region as your Neo4j Aura instance.

Storage is adjustable independent of memory for AuraDB pre-paid billing on Google Cloud Platform (GCP), version 5.x. See xref:/managing-instances/instance-actions/#_flexible_storage[Flexible storage] for more information.

|Neo4j Aura automates the backup process (you can also create your own on-demand snapshots), storing your data securely in the cloud.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This repeats the previous row.

Ideally, the database should all fit into memory (page cache) for the best performance.
Keep an eye on this metric to make sure you have enough storage for today and for future growth.
Keep an eye on this metric to make sure you have enough storage for future growth.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What graph are you referring to?

Copy link
Collaborator

@AlexicaWright AlexicaWright left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Coming together nicely! But what about versioning? Neo4j 5.x? Not latest?

@neo-technology-commit-status-publisher
Copy link
Collaborator

This PR includes documentation updates
View the updated docs at https://neo4j-docs-aura-653.surge.sh

Updated pages:

@neo4j-docops-agent
Copy link
Collaborator

This PR includes documentation updates
View the updated docs at https://neo4j-docs-aura-653.surge.sh

Updated pages:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants