add benchmarks #114
Merged
add benchmarks #114
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: xieydd <xieydd@gmail.com>
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Contributor
There was a problem hiding this comment.
Pull Request Overview
This pull request adds benchmark documentation pages to showcase VectorChord's performance compared to various alternatives.
- Added benchmark sections for Price, Performance, pgvector, pgvectorscale, and Elasticsearch.
- Updated the sidebar configuration to include a new "Benchmarks" section.
Reviewed Changes
Copilot reviewed 7 out of 7 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| src/vectorchord/index.md | Added benchmark navigation links. |
| src/vectorchord/benchmark/price.md | New price benchmark documentation. |
| src/vectorchord/benchmark/pgvectorscale.md | New benchmark page for pgvectorscale with a naming typo. |
| src/vectorchord/benchmark/pgvector.md | New benchmark page for pgvector with duplicated text in heading. |
| src/vectorchord/benchmark/performance.md | New performance benchmark documentation with a grammar issue. |
| src/vectorchord/benchmark/elasticsearch.md | New benchmark page for Elasticsearch with a phrasing mistake. |
| .vitepress/config.mts | Updated sidebar configuration to add the Benchmarks section. |
Comments suppressed due to low confidence (2)
src/vectorchord/benchmark/pgvectorscale.md:23
- Typo: 'pgvectorsale' should be 'pgvectorscale' to match the correct extension name.
VectorChord maximizes CPU usage, reduces memory consumption, and shortens index-building time compared to pgvectorsale.
src/vectorchord/benchmark/performance.md:21
- [nitpick] The sentence is grammatically unclear; consider rephrasing to 'If you are interested in VectorChord's scalability, please refer to our blog […]'.
If you are interested VectorChord scalable capability, you can refer our blog [Vector Search at 10,000 QPS in PostgreSQL with VectorChord].
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Signed-off-by: xieydd <xieydd@gmail.com>
Deploying pgvecto-rs-docs with
|
| Latest commit: |
4bbb1b6
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://3f3af6d6.pgvecto-rs-docs.pages.dev |
| Branch Preview URL: | https://add-benchmark.pgvecto-rs-docs.pages.dev |
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Signed-off-by: xieydd <xieydd@gmail.com>
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR introduces benchmarking documentation and updates the navigation for benchmark pages.
- Added a new "Benchmarks" section with links in the homepage and navigation.
- Introduced benchmark markdown pages for price, performance, pgvector, Elasticsearch, and pgvectorscale.
- Updated the VitePress configuration to include the new benchmark links.
Reviewed Changes
Copilot reviewed 7 out of 7 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| src/vectorchord/index.md | Added a new Benchmarks section with links to benchmark markdown pages. |
| src/vectorchord/benchmark/price.md | Introduced price benchmark documentation. |
| src/vectorchord/benchmark/pgvectorscale.md | Added benchmark content for pgvectorscale (note potential typo). |
| src/vectorchord/benchmark/pgvector.md | Added benchmark content for pgvector. |
| src/vectorchord/benchmark/performance.md | Added performance benchmark documentation. |
| src/vectorchord/benchmark/elasticsearch.md | Added benchmark documentation for Elasticsearch. |
| .vitepress/config.mts | Updated navigation structure to include benchmarks. |
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Signed-off-by: xieydd <xieydd@gmail.com>
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR adds a dedicated Benchmarks section to the documentation, detailing performance and cost comparisons between VectorChord and other vector database solutions.
- New benchmark pages for Price, Performance, pgvector, pgvectorscale, and Elasticsearch have been introduced.
- The main index and sidebar configuration have been updated to include navigation for the new benchmarks.
Reviewed Changes
Copilot reviewed 7 out of 7 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| src/vectorchord/index.md | Added a Benchmarks section with links to benchmark pages. |
| src/vectorchord/benchmark/price.md | Introduced benchmark details including pricing comparisons. |
| src/vectorchord/benchmark/pgvectorscale.md | Added a detailed benchmark comparing pgvectorscale. |
| src/vectorchord/benchmark/pgvector.md | Introduced benchmark for pgvector with performance metrics. |
| src/vectorchord/benchmark/performance.md | Detailed performance benchmarks across several datasets. |
| src/vectorchord/benchmark/elasticsearch.md | Added benchmark page comparing VS BM25 with Elasticsearch. |
| .vitepress/config.mts | Updated sidebar configuration to include the Benchmarks menu. |
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Signed-off-by: xieydd <xieydd@gmail.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Signed-off-by: xieydd <xieydd@gmail.com>
gaocegege
reviewed
May 13, 2025
Signed-off-by: xieydd <xieydd@gmail.com>
Signed-off-by: xieydd <xieydd@gmail.com>
gaocegege
approved these changes
May 15, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
merge after #113