Clarification on Safety and Performance of OOM Monitor and .dat File Size on iOS

[canhth]

Issue /提问须知

I'm trying Matrix iOS/macOS framework for monitoring out-of-memory (OOM) usage and have a few concerns and questions regarding its safety and performance in a production environment.
I would greatly appreciate your clarification on the following:

1. OOM Monitor in Release mode

As the documentation said, WCMemoryStatPlugin uses private APIs, which are disabled in Release mode to avoid App Store audit issues.

• Question: Does this mean the OOM monitor feature of Matrix is only intended for Debug builds? Is there any risk or limitation when using it in production without the private API (in Release mode)?

2. Size of .dat Records

I have noticed that the size of .dat files generated during testing is quite large. For a simple demo app, some .dat files exceed 700MB in size.

• Question 1: Is it safe to allow these large .dat files in a production environment?
• Question 2: Is there a way to reduce the size of these .dat files, such as limiting the amount of data logged, or applying filters?

3. Performance Impact

The latest available performance data regarding CPU and memory usage was shared in the documentation:

WCMemoryStatPlugin has a CPU usage of about 13% when running in the iPhone 6 Plus. This is related to the amount of data generated by the application. The amount of data generated is large, which may result in slightly higher CPU usage.
WCMemoryStatPlugin uses mmap to map files to memory, with around 20MB memory occupation.

• Question: Are there any recent updates on how the CPU and memory usage of WCMemoryStatPlugin affects performance, especially on modern devices and larger applications?