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.