Skip to content

feat: add a empirical formula about estimated memory usage #151

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.

Sign up for GitHub

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

Closed
wants to merge 1 commit into from
Closed

feat: add a empirical formula about estimated memory usage #151

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions src/vectorchord/usage/indexing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -88,8 +88,6 @@ SET vchordrq.probes TO '10';
SELECT * FROM items ORDER BY embedding <=> '[3,1,2]' LIMIT 10;
```

For large tables, the `build.internal` process costs huge time and memory. You can refer to [External Build](external-index-precomputation) to have a better experience.

For large tables, you may opt to use more shared memory to accelerate the process by setting `build.pin` to `true`.

```sql
Expand All @@ -103,6 +101,10 @@ build_threads = 8
$$);
```

For large tables, the `build.internal` process costs huge time and memory. Let the dimension be `D`, `build.internal.lists[-1]` be `C`, `build.internal.sampling_factor` be `F`, and `build.internal.threads` be `T`. The memory consumption is approximately `4CD(F + T + 1)` bytes.

You can also refer to [External Build](external-index-precomputation) to offload the indexing workload to other machines.

## Reference

### Operator Classes <badge type="info" text="vchordrq" /> {#operator-classes}
Expand Down