openzipkin/zipkin

Add benchmarks

Open

#1,226 创建于 2016年8月10日

在 GitHub 查看
 (5 评论) (0 反应) (0 负责人)Java (16,912 star) (3,079 fork)batch import
help wanted

描述

From @adriancole on November 17, 2015 3:21

Some aspects of code need to be benchmarked as they will be run a lot.

Here's some ideas... feel free to contribute!

For each scenario, use traces of 1-5 depth and 10-200 width, where spans range from local to remote w/up to 2KB annotation sizes.

Library Microbenchmarks:

  • thrift and json codec
  • time skew adjustment

Integration Benchmarks (ex server running against each spanstore impl)

  • accepts/second for 1, 10, 100 length spans in json vs thrift
  • at rest size of 10K - 1M traces:
  • service/span name query latency
  • duration query latency
  • dependency query latency

Copied from original issue: openzipkin/zipkin-java#45

贡献者指南

技术栈
java
领域
performancetesting
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
3-5 days
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
JavaJMH
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
40
研究方向
This issue requests adding benchmarks for Zipkin library components and integration tests. Start by setting up JMH (Java Microbenchmark Harness) as the benchmarking framework. Focus on the microbenchmarks first: Thrift and JSON codec performance, and time skew adjustment. Reference existing test files in the repository for setup. For integration benchmarks, you'll need to run a Zipkin server against span store implementations (e.g., Elasticsearch, Cassandra). The original issue (openzipkin/zipkin java#45) may have additional discussion. After implementing a benchmark for one scenario, seek maintainer feedback before expanding.
Add benchmarks · openzipkin/zipkin#1226 | Good First Issue