openzipkin/zipkin

Create Rally benchmark for Elasticsearch storage

Open

#1354 opened on Oct 26, 2016

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Java (16,912 stars) (3,079 forks)batch import
help wanted

Description

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!!

Contributor guide

Tech stack
javaelasticsearch
Domain
performancetesting
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Java basicsElasticsearch knowledgeRally understanding
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35
Research direction
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.