/third_party/node/lib/internal/perf/ |
D | event_loop_utilization.js | 11 return { idle: 0, active: 0, utilization: 0 }; 17 return { idle, active, utilization: active / (idle + active) }; 24 return { idle, active, utilization: active / (idle + active) }; 29 const utilization = active_delta / (idle_delta + active_delta); 30 return { idle: idle_delta, active: active_delta, utilization };
|
/third_party/node/test/parallel/ |
D | test-performance-eventlooputil.js | 18 assert.deepStrictEqual(elu, { idle: 0, active: 0, utilization: 0 }); property 20 { idle: 0, active: 0, utilization: 0 }); property 22 { idle: 0, active: 0, utilization: 0 }); property 48 assert.strictEqual(elu2.utilization, 1); 49 assert.strictEqual(elu4.utilization, 1); 67 assert.strictEqual(elu1.utilization, elu1.active / sum); 89 assert.strictEqual(elu3.utilization,
|
D | test-crypto-secure-heap.js | 48 assert(b.utilization > 0.0);
|
/third_party/node/lib/internal/ |
D | worker.js | 503 return { idle: 0, active: 0, utilization: 0 }; 510 return { idle: 0, active: 0, utilization: 0 }; 516 return { idle, active, utilization: active / (idle + active) }; 528 return { idle, active, utilization: active / (idle + active) }; 533 const utilization = active_delta / (idle_delta + active_delta); 534 return { idle: idle_delta, active: active_delta, utilization };
|
/third_party/openGLES/extensions/NVX/ |
D | NVX_gpu_memory_info.txt | 53 approaching full utilization and swapping (with its related 57 hardware memory utilization in order to allow the application to 118 the overall GPU memory utilization so that an application can determine 155 any potential fragmentation issues that may limit full utilization
|
/third_party/skia/third_party/externals/opengl-registry/extensions/NVX/ |
D | NVX_gpu_memory_info.txt | 53 approaching full utilization and swapping (with its related 57 hardware memory utilization in order to allow the application to 118 the overall GPU memory utilization so that an application can determine 155 any potential fragmentation issues that may limit full utilization
|
/third_party/node/lib/internal/crypto/ |
D | util.js | 550 return { total: 0, used: 0, utilization: 0, min: 0 }; 554 const utilization = used / total; 555 return { total, used, utilization, min };
|
/third_party/openGLES/extensions/QCOM/ |
D | QCOM_binning_control.txt | 88 utilization (this path increases vertex 91 utilization (this path increases CPU
|
/third_party/skia/third_party/externals/opengl-registry/extensions/QCOM/ |
D | QCOM_binning_control.txt | 88 utilization (this path increases vertex 91 utilization (this path increases CPU
|
/third_party/ltp/testcases/kernel/power_management/lib/ |
D | pm_sched_mc.py | 718 utilization = int(stats_percentage[l][1]) 720 utilization += int(get_cpu_utilization("cpu%s" %sib_list[i])) 722 utilization = stats_percentage[l][1] 723 if utilization > 40:
|
/third_party/node/test/sequential/ |
D | test-worker-eventlooputil.js | 67 { idle: 0, active: 0, utilization: 0 }); property
|
/third_party/mesa3d/docs/ |
D | perfetto.rst | 13 - Process memory utilization (``linux.process_stats``) 18 GPU performance (frequency, utilization, performance counters, etc) on the
|
/third_party/vk-gl-cts/external/vulkan-docs/src/appendices/ |
D | VK_NV_inherited_viewport_scissor.txt | 24 resizing and want to improve utilization of re-usable secondary command
|
D | VK_NV_inherited_viewport_scissor.adoc | 24 resizing and want to improve utilization of reusable secondary command
|
/third_party/node/doc/api/ |
D | perf_hooks.md | 96 * `utilization` {number} 100 high resolution milliseconds timer. The `utilization` value is the calculated 110 and `idle` times, as well as the corresponding `utilization` value are 118 ELU is similar to CPU utilization, except that it only measures event loop 132 console.log(eventLoopUtilization(elu).utilization); 137 `utilization` is `1`. This is because the call to
|
D | worker_threads.md | 1118 * `utilization` {number} 1124 is done within the event loop. So the event loop utilization is 1153 The event loop utilization of a worker is available only after the [`'online'`
|
/third_party/nghttp2/doc/ |
D | h2load.h2r | 112 disables flow control to avoid under utilization of server
|
D | h2load.1.rst | 427 disables flow control to avoid under utilization of server
|
/third_party/mesa3d/docs/isl/ |
D | aux-surf-comp.rst | 28 instead. Depending on the geometry and cache utilization, this can save as
|
/third_party/openGLES/extensions/SGI/ |
D | GLX_SGI_cushion.txt | 34 frames. In particular, they monitor the utilization of graphics
|
/third_party/skia/third_party/externals/opengl-registry/extensions/SGI/ |
D | GLX_SGI_cushion.txt | 34 frames. In particular, they monitor the utilization of graphics
|
/third_party/skia/third_party/externals/swiftshader/third_party/marl/ |
D | README.md | 144 Multiple `marl::Scheduler`s may fight each other for hardware thread utilization.
|
/third_party/skia/third_party/externals/opengl-registry/extensions/SGIS/ |
D | SGIS_texture_select.txt | 40 The purpose of this extension is allow better utilization of texture
|
/third_party/openGLES/extensions/SGIS/ |
D | SGIS_texture_select.txt | 40 The purpose of this extension is allow better utilization of texture
|
/third_party/skia/third_party/externals/opengl-registry/extensions/AMD/ |
D | GLX_AMD_gpu_association.txt | 157 distributed GPU utilization.
|