Original Summary

Hi everyone, we’ve just open-sourced two command-line tools, one for benchmarking Elasticsearch performance and one for creating Elasticsearch indexes from Common Crawl data.<p>Benchmarker: <a href="https:&#x2F;&#x2F;github.com&#x2F;Vesiro&#x2F;vesiro-benchmarker" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;Vesiro&#x2F;vesiro-benchmarker</a> Indexer: <a href="https:&#x2F;&#x2F;github.com&#x2F;Vesiro&#x2F;vesiro-indexer" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;Vesiro&#x2F;vesiro-indexer</a><p>We’re building a product designed to improve Elasticsearch performance, and needed a consistent way to create test indexes and rerun search workloads after making changes to our setup. You can use vesiro-benchmarker to run repeatable search benchmarks against an existing Elasticsearch index, and vesiro-indexer is designed to create Elasticsearch indexes from Common Crawl data.<p>For us, reproducibility in our benchmarking is very important. This is why we chose Common Crawl as a data source, as it enables other people to obtain the source data and inspect how we build test indexes. It also doesn’t hurt that there is tons of Common Crawl data, so we can index very large amounts.<p>Depending on your needs, you might not need both tools. If you already have your own indexes and just need a simple way to start benchmarking, the benchmarker will be enough. If you are only looking for a way to set up test indexes you might be fine just using the indexer.<p>We are interested to hear how these tools fit the way other teams benchmark Elasticsearch. Feedback on the query workloads or the Common Crawl indexing setup would be particularly helpful.

  • 情报分类：技术学习与提效
  • 分类依据：内容涉及技术、AI、软件工具或工程实践
  • 信息来源：Hacker News 新项目
  • 发布时间：2026/10/1 22:07:50