CPU usage and disk I/O were identified as potentially useful metrics. However, not much thinking went into defining those metrics during the design phase. Both could be represented graphically with histograms, but it is unclear what data we can collect. For example, is it possible to distinguish build activity from other system activity happening in the same hardware?
Created attachment 1266 [details] CPU and Disk I/O information
Created attachment 1272 [details] CPU and Disk I/O information
Created attachment 1415 [details] Design 1.7 Build CPU usage
Created attachment 1416 [details] Design 1.8 Build disk I/O
Created attachment 1510 [details] Design 1.7 Build CPU usage
Created attachment 1511 [details] Design 1.8 Build disk I/O
Created attachment 1674 [details] Design 1.7 Build CPU usage
Created attachment 1675 [details] Design 1.8 Build disk I/O
Created attachment 1680 [details] Design 1.7 Build CPU usage
Created attachment 1681 [details] Design 1.8 Build disk I/O
Created attachment 1723 [details] Sorting the "CPU usage" table
Created attachment 1724 [details] Sorting the "Disk I/O" table
The filters in the CPU usage and Disk I/O tables are the same as in the tasks table. See bug 4278 for design documentation.
Created attachment 1756 [details] Searching the "CPU" table Uploading search design spec for CPU usage table.
Created attachment 1757 [details] Searching the "disk I/O" table Uploading search design spec for disk I/O table.
Verified. Cheers, IonutC