aurora-reviews mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ben Mahler" <>
Subject Re: Review Request 33608: Added a status update throughput benchmark.
Date Tue, 05 May 2015 22:24:31 GMT

This is an automatically generated e-mail. To reply, visit:

(Updated May 5, 2015, 10:24 p.m.)

Review request for Aurora and Maxim Khutornenko.


Added a maybeSleep() per Bill's request.

Bugs: AURORA-1283

Repository: aurora


In order to justify doing asynchronous batch acknowledgements and to better understand status
update throughput, this introduces a benchmark.

Note that this assumes that status update processing is not synchronous, so that the benchmark
doesn't need to be updated for AURORA-1228.

Diffs (updated)

  src/jmh/java/org/apache/aurora/benchmark/ PRE-CREATION 
  src/jmh/java/org/apache/aurora/benchmark/fakes/ PRE-CREATION 
  src/jmh/java/org/apache/aurora/benchmark/fakes/ PRE-CREATION 
  src/main/java/org/apache/aurora/scheduler/ c54619f7cd617b48069363173dcf63b6254b4095

  src/main/java/org/apache/aurora/scheduler/mesos/ d7d659bb13f085ff06291ef0033572f8bdf29874



Ran the benchmarks against the existing code and some pending code I have for AURORA-1228
to demonstrate the improvement.

The end to end tests are broken, appears to be unrelated to my change from what I can tell.


Ben Mahler

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message