<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>vectorsearch on Vchord</title>
    <link>https://vchord.pgsty.com/tags/vectorsearch/</link>
    <description>Recent content in vectorsearch on Vchord</description>
    <generator>Hugo</generator>
    <language>en-US</language>
    
    
    
      <lastBuildDate>Mon, 02 Nov 2026 19:35:19 +0800</lastBuildDate>
    
    
      <atom:link href="https://vchord.pgsty.com/tags/vectorsearch/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
        <title>How We Made 100M Vector Indexing in 20 Minutes Possible on PostgreSQL</title>
        <link>https://vchord.pgsty.com/blog/post/how-we-made-100m-vector-indexing-in-20-minutes-possible-on-postgresql/</link>
        <pubDate>Wed, 03 Dec 2025 00:00:00 +0000</pubDate>
        
        <guid>https://vchord.pgsty.com/blog/post/how-we-made-100m-vector-indexing-in-20-minutes-possible-on-postgresql/</guid>
        <description>&lt;h2 id=&#34;1-introduction&#34;&gt;1. Introduction&#xA;&lt;/h2&gt;&#xA;&lt;p&gt;In the past few months, we’ve heard consistent feedback from users and partners: while our goal of providing a scalable, high-performance alternative to pgvector is well-received, index build time and memory usage remain major concerns at billion-scale.&lt;/p&gt;&#xA;&lt;p&gt;Now VectorChord can index 100 million 768-dimensional vectors in 20 minutes on a 16 vCPU machine with just 12 GB of memory. By contrast, indexing the same data with pgvector requires around 200 GB of memory and about 40 hours on a 16-core instance. And pgvector with insufficient memory often suffer from page swapping, making builds even slower.&lt;/p&gt;</description>
      </item>
    <item>
        <title>Introducing Vechord: Turn PostgreSQL into your search engine in a Pythonic way.</title>
        <link>https://vchord.pgsty.com/blog/post/introducing-vechord-turn-postgresql-into-your-search-engine-in-a-pythonic-way/</link>
        <pubDate>Wed, 23 Apr 2025 00:00:00 +0000</pubDate>
        
        <guid>https://vchord.pgsty.com/blog/post/introducing-vechord-turn-postgresql-into-your-search-engine-in-a-pythonic-way/</guid>
        <description>&lt;p&gt;Today, we&amp;rsquo;re thrilled to announce the release of &lt;a href=&#34;https://github.com/tensorchord/vechord&#34;&gt;&lt;strong&gt;Vechord&lt;/strong&gt;&lt;/a&gt;, a new Python library designed to dramatically simplify building robust search infrastructure directly on top of the PostgreSQL database.&lt;/p&gt;&#xA;&lt;p&gt;In the rapidly evolving world of AI and large language models (LLMs), Retrieval-Augmented Generation (RAG) and semantic search have become crucial components. However, setting up the necessary vector search infrastructure often involves learning new database technologies, managing complex integrations, or wrestling with intricate frameworks. This adds friction and slows down development, especially for teams already comfortable with PostgreSQL.&lt;/p&gt;</description>
      </item>
    <item>
        <title>Vector Search at 10,000 QPS in PostgreSQL with VectorChord</title>
        <link>https://vchord.pgsty.com/blog/post/vector-search-at-10000-qps-in-postgresql-with-vectorchord/</link>
        <pubDate>Thu, 27 Feb 2025 00:00:00 +0000</pubDate>
        
        <guid>https://vchord.pgsty.com/blog/post/vector-search-at-10000-qps-in-postgresql-with-vectorchord/</guid>
        <description>&lt;p&gt;VectorChord is a PostgreSQL extension designed for scalable, high-performance, and disk-efficient vector similarity search, and serves as the successor to &lt;a href=&#34;https://github.com/tensorchord/pgvecto.rs&#34;&gt;pgvecto.rs&lt;/a&gt;. In our previous &lt;a href=&#34;https://vchord.pgsty.com/blog/post/vectorchord-store-400k-vectors-for-1-in-postgresql/&#34;&gt;blog post&lt;/a&gt;, we showed that with just $250 per month, VectorChord achieved 131 QPS with 0.95 precision on 100 million vectors—demonstrating impressive cost-effective performance for large-scale vector search.&lt;/p&gt;&#xA;&lt;img class=&#34;td-image&#34; src=&#34;https://cdn.hashnode.com/res/hashnode/image/upload/v1733194599461/eb1cf21d-4eb0-4427-8b39-bbb96d125182.png?auto=compress,format&amp;amp;format=webp&#34; alt=&#34;&#34; loading=&#34;lazy&#34; decoding=&#34;async&#34;&gt;&lt;p&gt;Building on that success, this post focuses on high performance by exploring how VectorChord can &lt;strong&gt;reach 10,000 QPS in PostgreSQL&lt;/strong&gt;. We’ll walk you through how PostgreSQL’s reliable relational foundation integrates with advanced vector indexing to deliver fast, scalable search capabilities, and provide a production-ready setup along with a detailed architecture guide for managing large-scale vector computations even under heavy loads.&lt;/p&gt;</description>
      </item>
    <item>
        <title>Benefits and Steps of External Centroids Building in VectorChord</title>
        <link>https://vchord.pgsty.com/blog/post/benefits-and-steps-of-external-centroids-building-in-vectorchord/</link>
        <pubDate>Tue, 10 Dec 2024 00:00:00 +0000</pubDate>
        
        <guid>https://vchord.pgsty.com/blog/post/benefits-and-steps-of-external-centroids-building-in-vectorchord/</guid>
        <description>&lt;p&gt;Clustering is an important component in vector search, and the k-means algorithm remains one of the most widely used techniques. However, its simplicity comes with a significant drawback: resource-intensive computation can render it impractical for large datasets. This blog explores why this challenge arises and how leveraging external builds to overcome it. We also share insights into our approach to implementing this solution.&lt;/p&gt;&#xA;&lt;h3 id=&#34;why-we-need-it&#34;&gt;Why we need it&#xA;&lt;/h3&gt;&#xA;&lt;img class=&#34;td-image&#34; src=&#34;https://cdn.hashnode.com/res/hashnode/image/upload/v1733711948118/a8ca38d3-580f-4f20-90b9-03c826289a7c.png&#34; alt=&#34;&#34; loading=&#34;lazy&#34; decoding=&#34;async&#34;&gt;&lt;p&gt;VectorChord uses IVF + RaBitQ to perform vector search. The quality of the IVF cluster can heavily affect search precision and speed. K-means usually takes dozens of rounds before convergence. For each round, all the sampled vectors need to be assigned to the nearest cluster. This is the most computationally intensive part. The good news is that this process can be easily parallelized.&lt;/p&gt;</description>
      </item>
    <item>
        <title>pgvecto.rs 0.2: Unifying Relational Queries and Vector Search in PostgreSQL</title>
        <link>https://vchord.pgsty.com/blog/release/pgvectors-02-unifying-relational-queries-and-vector-search-in-postgresql/</link>
        <pubDate>Tue, 20 Feb 2024 00:00:00 +0000</pubDate>
        
        <guid>https://vchord.pgsty.com/blog/release/pgvectors-02-unifying-relational-queries-and-vector-search-in-postgresql/</guid>
        <description>&lt;p&gt;We are excited to announce the release of &lt;a href=&#34;https://vchord.pgsty.com/pgvecto-rs/&#34;&gt;pgvecto.rs&lt;/a&gt; 0.2, a significant milestone in the journey of bridging the gap between relational queries and vector search in PostgreSQL. This update brings together the power of both worlds, offering enhanced efficiency and enabling complex queries within PostgreSQL.&lt;/p&gt;&#xA;&lt;p&gt;In the past, developers and data scientists encountered the significant challenge of managing separate systems for relational queries and vector search. This resulted in increased complexity and resource overhead. However, with the release of &lt;a href=&#34;https://vchord.pgsty.com/pgvecto-rs/&#34;&gt;pgvecto.rs&lt;/a&gt; 0.2, we have addressed this issue by integrating the cutting-edge &lt;a href=&#34;https://www.usenix.org/conference/osdi23/presentation/zhang-qianxi&#34;&gt;VBASE method from OSDI 2023&lt;/a&gt;. This integration has substantially refined the efficiency of vector search within PostgreSQL.&lt;/p&gt;</description>
      </item>
    
  </channel>
</rss>
