Memory & events tracing in mus |
||||
Issue descriptionIn current chrome, we can trace system memory & GPU memory usage for every process. How do we tracing them in mus world? In current chrome, for GPU memory, every GPU client process has unique tracing ID. The GPU process will use this ID to tracing allocations done on behalf of the connecting process. This so we can correctly attribute memory to the process. This needs to be thought about more generally in the mus design.
,
Feb 26 2018
,
Feb 26 2018
,
Aug 13
I believe all this works correctly now. |
||||
►
Sign in to add a comment |
||||
Comment 1 by rjkroege@chromium.org
, Oct 4 2016Labels: Proj-Mustash