openzipkin/zipkin

Create Rally benchmark for Elasticsearch storage

Open

#1,354 opened on Oct 26, 2016

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

Repository metrics

Stars
 (16,912 stars)
PR merge metrics
 (No merged PRs in 30d)

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

Research direction
Explore how to set up Rally benchmarks for Elasticsearch storage in Zipkin. Understand the existing storage operations and design a benchmark configuration.
Tech stack
java
Domain
backenddatabase
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitJavaElasticsearch
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50