Skip to content

Dev memory config vector indexes #2289

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 4 commits into
base: dev
Choose a base branch
from

Conversation

renetapopova
Copy link
Collaborator

No description provided.

@mauvo
Copy link
Contributor

mauvo commented Apr 29, 2025

  • Let's add a link back to the vector index documentation. And we need a link from the vector index documentation to the memory config page.

I think this is clearer, that we're agreeing with the memory config section, not contradicting it.
@mauvo
Copy link
Contributor

mauvo commented Apr 29, 2025

  • I think "Warming up the vector index", should be moved to below the content that is directly discussing memory configuration. Probably it should be moved to the bottom of the page.

However, you can also warm up the index by running a few random queries to help the OS load the index into memory.
The number of queries required to warm up the index depends on the size of the index and the amount of memory available.
For a smaller index (up to 1M entries), five queries should be sufficient to load the index into memory.
For a larger index, you may need to run a hundred queries.
Copy link
Contributor

Choose a reason for hiding this comment

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

I think we can remove the last two lines here, they feel a little imprecise.

For a larger index, you may need to run a hundred queries. It is also recommended to test the index.

For a larger index, you may need to run a hundred queries.
It is also recommended to test the index.

[NOTE]
Copy link
Contributor

Choose a reason for hiding this comment

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

I think I'd cut out this Note. People who run into this situation will probably figure it out, and otherwise it just adds complexity without contributing a clear solution.

I think we mean that the machine must have sufficient memory. Saying OS could be confused with the OS memory we say Lucene requires.
@neo4j-docops-agent
Copy link
Collaborator

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

New pages:

Updated pages:

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

Successfully merging this pull request may close these issues.

3 participants