OLD | NEW |
---|---|
(Empty) | |
1 // Copyright 2017 The Chromium Authors. All rights reserved. | |
2 // Use of this source code is governed by a BSD-style license that can be | |
3 // found in the LICENSE file. | |
4 | |
5 // Protocol for process resource usage. | |
6 | |
7 syntax = "proto2"; | |
8 | |
9 option optimize_for = LITE_RUNTIME; | |
10 | |
11 package remoting.protocol; | |
12 | |
13 // The resource usage of a single process. | |
14 // Next Id: 5 | |
15 message ProcessResourceUsage { | |
16 // The name or friendly name of the process. | |
17 optional string process_name = 1; | |
18 | |
19 // The processor usage. It should be a consistent value on all platforms in | |
20 // range of 0 to (100 * NumCPUCores). | |
21 optional double processor_usage = 2; | |
22 | |
23 // Memory usage of working set. | |
24 optional uint64 working_set_size = 3; | |
25 | |
26 // Memory usage of page file. | |
27 optional uint64 pagefile_size = 4; | |
28 } | |
29 | |
30 // The resource usage of several processes. | |
31 // Next Id: 6 | |
32 message AggregatedProcessResourceUsage { | |
33 // A friendly name of the processes current instance aggregated from. | |
34 optional string name = 1; | |
joedow
2017/04/24 17:16:09
I'm not sure how useful the aggregate is and wheth
Hzj_jie
2017/04/25 00:17:54
Yes, each individual usage is recorded in |usages|
| |
35 | |
36 // The total processor usage. | |
37 optional double processor_usage = 2; | |
38 | |
39 // The total memory usage of working set. | |
40 optional uint64 working_set_size = 3; | |
41 | |
42 // The total memory usage of page file. | |
43 optional uint64 pagefile_size = 4; | |
44 | |
45 // The process resource usage of each individual process. | |
46 repeated ProcessResourceUsage usages = 5; | |
47 } | |
OLD | NEW |