MemoryUsageDetails object structure
The MemoryUsageDetails object has three properties: count (number), size (number), and liveSize (number). This object is used to report memory usage details in Electron applications.
Electron · Tutorial · all subjects
performance & native modules
4 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.
EnableHeapProfilingOptions mode values and scope
The mode option controls which processes are profiled and has the following values: 'all' profiles all processes, 'browser' profiles only the browser process, 'gpu' profiles only the GPU process, 'minimal' profiles only the browser and GPU processes, 'renderer-sampling' profiles at most 1 renderer process with fixed probability, 'all-renderers' profiles all renderer processes, 'utility-sampling' profiles each utility process with fixed probability, 'all-utilities' profiles all utility processes, and 'utility-and-browser' profiles all utility processes and the browser process. The default value is 'all'. This option is equivalent to --memlog in Chrome.
EnableHeapProfilingOptions samplingRate configuration
The samplingRate option controls the sampling interval in bytes. The default is 100000 (100KB), which is enough to observe allocation sites that make allocations greater than 500KB total. The samplingRate must be an integer between 1000 and 10000000. Lower intervals produce more precise profiles but at a cost to performance. This option is equivalent to --memlog-sampling-rate in Chrome.
EnableHeapProfilingOptions stackMode values
The stackMode option controls the type of metadata recorded for each allocation and has the following values: 'native' records instruction addresses from unwinding the stack, and 'native-with-thread-names' records instruction addresses from unwinding the stack and includes the thread name as the first frame. The default value is 'native'. This option is equivalent to --memlog-stack-mode in Chrome.