PulseAugur
实时 22:04:12
English(EN) We accelerated CobbleDB development with a team of proactive coding agents.

Perplexity 开源 CobbleDB,大幅降低延迟并使用 AI 代理进行开发 · 跟踪 7 个来源

Perplexity 开发并开源了 CobbleDB,这是一种专为高效批量读取设计的新型键值数据库,显著提高了其搜索工作负载的性能。这个新系统取代了 Amazon DynamoDB,将中位数批量读取延迟从 31.4 毫秒大幅降低到 5.60 毫秒,并将 p99 延迟从 123 毫秒降低到 24.2 毫秒。CobbleDB 的开发得到了 AI 代理团队的加速,核心基础设施由两名工程师和数百个此类代理在两个月内完成。 AI

影响 加速了 AI 搜索性能,并为开发人员提供了一个新工具,有可能提高 AI 相关应用程序的效率。

排序理由 Perplexity 发布了一项新的数据库技术并详细介绍了其开发过程,这是一个产品发布/发布。

在 X — Perplexity 阅读 →

AI 生成摘要 · Google Gemini · 来自 7 个来源。 我们如何撰写摘要 →

Perplexity 开源 CobbleDB,大幅降低延迟并使用 AI 代理进行开发 · 跟踪 7 个来源

本文如何被排名

Signal score
7 / 100
Composite score across the factors below. Higher = stronger signal that this story matters right now.
Newsworthiness bucket
Tool
Perplexity 发布了一项新的数据库技术并详细介绍了其开发过程,这是一个产品发布/发布。
Source corroboration
7 independent sources
Strong cross-source corroboration — multiple independent publishers covered this within the clustering window.
Topics
infra, product
Editorial topic classification. Feeds into how the story surfaces on /topic/<slug> hub pages and into the per-entity coverage mix.
AI-industry relevance
High
Clearly on-topic for AI-industry coverage.
Story freshness
Breaking (< 6h)
Fresh story with cross-source coverage still developing. Ranking may shift as more sources report.

完整方法见我们的编辑标准

报道来源 [7]

  1. X — Perplexity TIER_1 English(EN) · perplexity_ai ·

    CobbleDB 专为准备好的页面记录的重复批量读取而构建,可优化 Perplexity 搜索工作负载的性能和成本。

    CobbleDB is purpose-built for repeated batch reads of prepared page records, optimizing performance and cost for Perplexity’s search workload. We plan to open-source CobbleDB for other teams building AI search. Read more: https://t.co/iK1dd8WDhR

  2. X — Perplexity TIER_1 English(EN) · perplexity_ai ·

    替换 DynamoDB 后,生产环境前后对比数据显示中位数批量读取延迟从 31.4 毫秒降至 5.60 毫秒,p99 从 123 毫秒降至 24.2 毫秒。

    After replacing DynamoDB, production before-and-after measurements show median batch-read latency falling from 31.4 to 5.60 ms and p99 from 123 to 24.2 ms. Our internal cost model estimates at least 20% savings relative to DynamoDB. https://t.co/Bs8c9vsRte

  3. X — Perplexity TIER_1 English(EN) · perplexity_ai ·

    这种分离允许每个副本以自己的节奏接收更新。

    That separation lets each replica ingest updates at its own pace. Pillar stores versioned document state in YTsaurus and queues exports. Lorry writes partitioned S3 batches that CobbleDB replicas apply independently and in order, so recovering nodes don’t delay others. https://t…

  4. X — Perplexity TIER_1 English(EN) · perplexity_ai ·

    优化读取也需要改变更新到达商店的方式。

    Optimizing reads also required changing how updates reached the store. We separated durable document state, update delivery, and serving across Pillar, Lorry, and CobbleDB. https://t.co/pL7vCBTyC3

  5. X — Perplexity TIER_1 English(EN) · perplexity_ai ·

    该架构优先考虑快速批量读取。CobbleDB 按分区对页面键进行分组,并通过 RocksDB MultiGet 并行读取它们。

    The architecture prioritizes fast batch reads. CobbleDB groups page keys by partition and reads them in parallel through RocksDB MultiGet. The router favors same-zone replicas and queries another copy when a replica is slow, so one delayed response need not hold up the batch. ht…

  6. X — Perplexity TIER_1 English(EN) · perplexity_ai ·

    我们通过一支积极主动的编码代理团队加速了 CobbleDB 的开发。

    We accelerated CobbleDB development with a team of proactive coding agents. The agents provided continuous inspection and follow-through across sessions under the direction of engineers responsible for architecture, review, and production authorization.

  7. X — Perplexity TIER_1 English(EN) · perplexity_ai ·

    我们正在发布关于如何构建 CobbleDB 的研究,这是我们为 Perplexity 搜索提供网络内容的关键值数据库。

    We’re publishing research on how we built CobbleDB, our key-value database that serves web content for Perplexity search. Two engineers and a team of hundreds of proactive, always-on AI agents built the core infrastructure in two months. https://t.co/OsCtY15UW6