hubcio opened a new issue, #1856: URL: https://github.com/apache/iggy/issues/1856
Currently, the `-H,--high-level-api` flag only works with consumer benchmarks, utilizing the `IggyConsumer` streaming API. This limits our ability to benchmark the complete high-level API surface. Current State: - ✅ High-level consumer API implemented (high_level_backend.rs) - ❌ Producer benchmarks still use low-level protocol calls - ❌ Producing consumer benchmarks use mixed APIs (low-level producer + high-level consumer) Proposed Enhancement: Implement high-level API backends for: 1. Producer benchmarks - Use `IggyProducer` streaming API instead of direct `send_messages()` calls 2. Producing consumer benchmarks - Use `IggyProducer` for message forwarding/transformation scenarios Benefits: - Complete high-level API performance validation - More realistic benchmarks for users adopting streaming abstractions - Consistent API usage patterns across all benchmark types - Better end-to-end latency measurements with stream-based producers Implementation Notes: - Follow existing `HighLevelBackend` pattern from consumer implementation - Ensure batch size consistency (currently validated for consumers only) - Maintain compatibility with existing low-level benchmarks - Add producer-specific high-level configuration options Acceptance Criteria: - `-H,--high-level-api` works with all producer benchmark types - Producing consumer uses high-level APIs for both production and consumption - Performance metrics remain accurate and comparable -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
