[Tracing benchmark] Put maxEventBytesPerCategory into diagnostics

[Tracing benchmark] Put maxEventBytesPerCategory into diagnostics

maxEventBytesPerCategory could change from one category to
another category in different runs. It is not suitable to 
be shown on the dashboard. This CL puts such information into 
the diagnostics, so when regression happens, people may still 
benefit from it.

BUG=catapult:#2078

Committed: https://chromium.googlesource.com/external/github.com/catapult-project/catapult/+/8d9e4952d037919b3e4c5167026c5a95baef93f9

[Zhen Wang, 2016-03-21 21:14:59]

Description was changed from

==========
Put per category info into diagnostics

BUG=catapult:#2078
==========

to

==========
[Tracing benchmark] Put per category info into diagnostics

Per category information could change from one run to
another. It is not suitable to be shown on the dashboard. 
This CL puts such information in the diagnostics, so when 
regression happens, people may still benefit from it.

BUG=catapult:#2078
==========

[Zhen Wang, 2016-03-21 21:17:33]

Description was changed from

==========
[Tracing benchmark] Put per category info into diagnostics

Per category information could change from one run to
another. It is not suitable to be shown on the dashboard. 
This CL puts such information in the diagnostics, so when 
regression happens, people may still benefit from it.

BUG=catapult:#2078
==========

to

==========
[Tracing benchmark] Put maxEventBytesPerCategory into diagnostics

maxEventBytesPerCategory could change from one category to
another category in different runs. It is not suitable to 
be shown on the dashboard. This CL puts such information into 
the diagnostics, so when regression happens, people may still 
benefit from it.

BUG=catapult:#2078
==========

[Zhen Wang, 2016-03-21 21:19:02]

zhenw@chromium.org changed reviewers:
+ eakuefner@chromium.org

[Zhen Wang, 2016-03-21 21:19:02]

ptal

[eakuefner, 2016-03-21 22:41:15]

lgtm

[Zhen Wang, 2016-03-21 22:41:35]

The CQ bit was checked by zhenw@chromium.org

[commit-bot: I haz the power, 2016-03-21 22:41:40]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1818923003/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1818923003/1

[commit-bot: I haz the power, 2016-03-21 23:13:22]

Description was changed from

==========
[Tracing benchmark] Put maxEventBytesPerCategory into diagnostics

maxEventBytesPerCategory could change from one category to
another category in different runs. It is not suitable to 
be shown on the dashboard. This CL puts such information into 
the diagnostics, so when regression happens, people may still 
benefit from it.

BUG=catapult:#2078
==========

to

==========
[Tracing benchmark] Put maxEventBytesPerCategory into diagnostics

maxEventBytesPerCategory could change from one category to
another category in different runs. It is not suitable to 
be shown on the dashboard. This CL puts such information into 
the diagnostics, so when regression happens, people may still 
benefit from it.

BUG=catapult:#2078

Committed:
https://chromium.googlesource.com/external/github.com/catapult-project/catapu...
==========

[commit-bot: I haz the power, 2016-03-21 23:13:23]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/external/github.com/catapult-project/catapu...