@@ -184,50 +184,4 @@ We have 3 dbs (shards), so real rates are:
1841843 * 10000 = 30 000 per second
1851853 * 15000 = 45 000 per second
186186```
187- ...which is quite a lot!
188-
189- As you can see in the results, we got pretty close to these rates:
190- ```
191- ...
192-
193- Publishing 300000 events with 5000 per second rate took: PT1M3.436S, which means 4729 per second rate
194- 3 runner instances were running in parallel, so the real rate was 14187 per second for 900000 events
195-
196- ...
197-
198- Waiting for consumption....
199-
200- ...
201-
202- Consumer of 2 partition is at the event 2588597, but latest event is 2590000; waiting for 1s...
203- Consumer of 3 partition is at the event 2589971, but latest event is 2589996; waiting for 1s...
204- Consumer of 3 partition is at the event 2589971, but latest event is 2589996; waiting for 1s...
205-
206- ...
207-
208- Consuming 300000 events with 5000 per second rate took: PT1M6.875S, which means 4486 per second rate
209- 3 runner instances were running in parallel, so the real rate was 13458 per second for 900000 events
210-
211- ...
212-
213- ...
214-
215- Publishing 600000 events with 10000 per second rate took: PT1M11.099S, which means 8438 per second rate
216- 3 runner instances were running in parallel, so the real rate was 25314 per second for 1800000 events
217-
218- ...
219-
220- Waiting for consumption....
221-
222- ...
223-
224- Consumer of 0 partition is at the event 3187024, but latest event is 3189999; waiting for 1s...
225-
226- ...
227-
228- Consuming 600000 events with 10000 per second rate took: PT1M12.561S, which means 8268 per second rate
229- 3 runner instances were running in parallel, so the real rate was 24804 per second for 1800000 events
230-
231- ...
232-
233- ```
187+ ...which is quite a lot!
0 commit comments