opensearch-project/OpenSearch

[Feature Request][GRPC] Add automated benchmark tests for GRPC APIs

Open

#19750 opened on Oct 23, 2025

View on GitHub
 (8 comments) (0 reactions) (1 assignee)Java (8,123 stars) (1,505 forks)batch import
Search:Performanceenhancementgood first issue

Description

Is your feature request related to a problem? Please describe

Currently gRPC APIs (Bulk and Search) do not run nightly benchmark tests. Adding these would be beneficial to catch performance degradations.

Describe the solution you'd like

Following https://github.com/opensearch-project/OpenSearch/blob/main/PERFORMANCE_BENCHMARKS.md, add the ability to:

  1. Run automated benchmarks nightly on the latest build distribution artifacts for 3.x.
  2. Publish results to dashboards for comparison (https://s12d.com/basline-dashboards)
  3. Trigger on-demand benchmarks for specific pull requests

Related component

Search:Performance

Describe alternatives you've considered

No response

Additional context

No response

Contributor guide

Tech stack
javagrpc
Domain
performancebackendci cd
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.
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.
mostly clear
Prerequisites
Java development experienceUnderstanding of gRPCFamiliarity with CI/CD pipelinesKnowledge of benchmarking practices
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
Examine the existing PERFORMANCE BENCHMARKS.md file at https://github.com/opensearch project/OpenSearch/blob/main/PERFORMANCE BENCHMARKS.md to understand the current pattern for running benchmarks. Then implement a similar setup for gRPC APIs, including automated nightly execution on the latest 3.x distribution artifacts. Use the same dashboard infrastructure referenced in the issue for publishing results. Also ensure on demand benchmarking for pull requests is triggered via CI/CD.