openzipkin/zipkin

Create Rally benchmark for Elasticsearch storage

Open

#1,354 建立於 2016年10月26日

在 GitHub 查看
 (1 留言) (0 反應) (0 負責人)Java (16,912 star) (3,079 fork)batch import
help wanted

描述

This likely should be in a separate repo, but might make sense here. If we create a benchmark for various storage operations, we could tell if an indexing, encoding or otherwise change helps or hurts.

https://github.com/elastic/rally

cc @openzipkin/elasticsearch help wanted!!

貢獻者指南

技術棧
javaelasticsearch
領域
performancetesting
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
3-5 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Java basicsElasticsearch knowledgeRally understanding
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
35
研究方向
Review the Rally documentation at https://github.com/elastic/rally to understand how to create a benchmark. Look at existing Rally benchmarks for inspiration, and identify the storage operations in Zipkin's Elasticsearch storage module (likely in zipkin storage/elasticsearch). The benchmark should measure indexing and query performance. Start by setting up a local Elasticsearch instance and Rally, then create a track that uses Zipkin's data format.