<p>Comments and suggestions</p>

<ul>
	<li>Cross check performance results occasionally with g4cpt (especially when there are big performance changes in a reference tag or an official release with respected to the previous reference).</li>
	<li>Provide a time series summary plot of performance changes (an example, CPU change by MR numbers), at least, for the last one month (year) or so.</li>
	<li>Configure the physics list or applications so as to reflect relevant changes in codes.</li>
	<li>Add a summary plot for changes in the total number of steps and tracks (preferably by the particle type)</li>
	<li>Add a summary for memory performance (total, peak and etc.) changes.</li>
	<li>Add other types of hardware (an example, Intel) if/as available on the open stack.</li>
	<li>Filler out any MR which may not require the CI performance run (for an example, change in scripts or other than actual codes changes which do not affect computing performance).</li>
	<li>Add an instruction how to monitor performance results in the stt shift page and in the geant-dev developer page.</li>
	<li>Advertise links to the CI performance page and a performance summary page from relevant geant4 internal pages.</li>
</ul>