This change adds a simple benchmark for the scheduler. It should aid in
identifying performance bottle necks (for example there's a heavily-used
string map) and to safeguard performance-sensitive changes. It has been
dormant for a while but I'd like to revive it and I'm looking for a
reviewer.

https://gerrit.cloudera.org/#/c/4554

Thanks, Lars

Reply via email to