Denovo1998 commented on issue #24600: URL: https://github.com/apache/pulsar/issues/24600#issuecomment-3591687762
I added load-testing support for “delayed messages” to the Pulsar driver of OpenMessaging Benchmark, including: * Fixed delay: All messages are delayed by a fixed duration; * Random delay: Each message is delayed randomly within a range; * Mixed ratio: Delayed messages and normal messages are mixed by ratio. For example configurations, please refer to: [https://github.com/Denovo1998/benchmark/blob/pulsar/driver-pulsar/pulsar-delayed-random-1s-10s.yaml](https://github.com/Denovo1998/benchmark/blob/pulsar/driver-pulsar/pulsar-delayed-random-1s-10s.yaml) ## Key configuration fields Use in Pulsar driver YAML or workload YAML: * messageDelayMs: Fixed delay (milliseconds); when > 0, fixed delay is enabled. * minMessageDelayMs / maxMessageDelayMs: Random delay range (milliseconds); when maxMessageDelayMs > 0, random delay is en abled. * delayMessageRatio: Proportion of delayed messages, value range 0.0 ~ 1.0: * 0.0 (default): All normal messages; * 0.3: About 30% delayed messages, 70% normal; * 1.0: All delayed messages. ## Typical scenario examples * All messages are randomly delayed for 1–10 seconds: Use the pulsar-delayed-random-1s-10s.yaml linked above (delayMessageRatio: 1.0). * 30% of messages are randomly delayed for 1–10 seconds: Set in the driver or workload: minMessageDelayMs: 1000 maxMessageDelayMs: 10000 delayMessageRatio: 0.3 -- 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]
