Lines Matching refs:be

3 This procedure should be followed when upgrading or moving to a new allocator.
8 [Performance Trace Benchmarks](#performance-trace-benchmarks) should be run.
13 systems and be a bit slower, but take less RSS. To enable the svelte config,
45 system. It is meant to be called after a call to `malloc_disable` to
62 implementation, but it should be a reasonable amount of time. The jemalloc
80 idea is that this can be called to purge memory that has not been
86 These are the tests that should be run to verify an allocator is
100 The allocation tests are not meant to be complete, so it is expected
101 that a native allocator will have its own set of tests that can be run.
136 address space is consumed. For 64 bit executables, this can be ignored.
140 benchmarks. These benchmarks can be built using this command:
147 For all of these benchmark runs, it can be useful to add these two options:
153 and helps to get a number that can be compared to the new allocator.
190 no outliers, but these numbers should not be used to make a final decision.
205 not be used as absolutes for determining if an allocator is worth using.
227 be modified in the future. It was chosen because a version of the native
252 This benchmark is designed to verify that the allocator will be performant
255 calls, and they tend to be on the critical path of applications.
267 These numbers should be as performant as the current allocator.
278 Calls to mallinfo are used in ART so a new allocator is required to be
283 mallinfo benchmark, it's not necessary for this to be better than the previous
284 allocator, only that the performance be in the same order of magnitude.
346 Every 100000 allocation operations, a dump of the RSS and VA space will be
347 performed. At the end, a final RSS and VA space number will be printed.
348 For the most part, the intermediate data can be ignored, but it is always
358 they should not be used as absolute value for comparison against the
359 current allocator. But, they should be in the same range as the current
369 current allocator. A small increase (on the order of a few MBs) would be okay.
389 The `GetNativeInfo` function needs to be modified to include the name
393 of a process, any named maps must be added to the file: