Open BruceDai opened 5 years ago
100 (or more) times
Maybe 100 times are too long to run, 20 times are enough?
consumption of op = GPU Memory Value1 ( memory after running CTS test cases 100 times )
- GPU Memory Value2 ( initial memory before running CTS test cases )
consumption of op = GPU Memory Value1 ( memory after running every time )
- GPU Memory Value2 ( initial memory after running first time )
It has memory leak if the value increase every time.
Maybe LeakSanitizer can help developer to debug where memory leak.
CPU memory (shared), GPU memory (MPS? ) -> Mapping to what kind of hardware
The Memory Footprint
in Task Manager reports Private Memory Footprint
as described in consistent memory metrics.
The definition of Private Memory Footprint
is:
So it doesn't include third-party library that is file-backed memory, but shared memory footprint
will be calculated accurately not over count, such as the GPU memory in Browser processor count only in Browser processor that doesn't count in GPU processor.
Do we lose memory consumption for native backend calls? -> System memory tools
It's too hard to estimate System memory as mentioned here:
The platonic ideal for this measurement includes memory used by both the kernel, and other system services on behalf of the process in question. Realistically, we have a hard time estimating the memory footprint contained in non-Chrome processes.
So my proposal is tested memory = memory footprint
+ GPU memory
in Browser, GPU and Render Processor.
Currently we refer to Estimating the private memory footprint of Chrome Linux, and use provided memory compute script to collect data on Linux platform. For Windows and macOS platforms, we also try this script
Here're some methods we tried to collect data.
This issue is filed for discussion about solution for collecting memory consumption by WebML API. QA firstly collected some memory consumption with Image Classification example likes:
This diff consumption memory may involve the memory for HTML rendering, so QA's method wasn't correct.
@fujunwei suggested develop a automation toolkit to only run CTS test cases 100 (or more) times one by one op to check memory consumption (leak)
@fujunwei Please help review my description of your solution. @huningxin @ibelem Please also take a review, thanks