Searched refs:spent (Results 1 – 25 of 128) sorted by relevance
123456
| /third_party/skia/platform_tools/android/apps/skottie/ |
| D | skottie_metric.proto | 36 // "render_time_avg_no_dequeue" tries to compensate the time spent to wait for a new buffer.
40 optional int64 ui_thread_cpu_time = 12; // CPU time spent on UI thread in nanoseconds
41 optional int64 rt_thread_cpu_time = 13; // CPU time spent on RenderThread in nanoseconds
42 optional int64 hwui_tasks_cpu_time = 14; // CPU time spent on hwuiTask0/1 threads in nanoseconds
43 optional int64 skottie_animator_cpu_time = 15; // CPU time spent on SkottieAnimator in ns
48 optional int64 total_gpu_time = 17; // GPU time spent to render all content in nanoseconds.
|
| /third_party/libuv/docs/src/ |
| D | metrics.rst | 8 spent idle in the kernel's event provider.
18 The return value is the accumulated time spent idle in the kernel's event
|
| /third_party/skia/third_party/externals/opengl-registry/extensions/SGIX/ |
| D | SGIX_bali_timer_instruments.txt | 26 measure the time spent in the geometry subsystem, and another
27 to measure the time spent in the rasterization subsystem. These
79 amount of time spent in geometry subsystem is maintained. A
83 The actual amount of time spent on geometry processing and
|
| /third_party/openGLES/extensions/SGIX/ |
| D | SGIX_bali_timer_instruments.txt | 26 measure the time spent in the geometry subsystem, and another
27 to measure the time spent in the rasterization subsystem. These
79 amount of time spent in geometry subsystem is maintained. A
83 The actual amount of time spent on geometry processing and
|
| /third_party/boost/libs/serialization/doc/ |
| D | profile1.txt | 26 self the average number of milliseconds spent in this
30 total the average number of milliseconds spent in this
64 the total amount of time spent in each function and its children.
76 % time This is the percentage of the `total' time that was spent
81 self This is the total amount of time spent in this function.
|
| D | profile3.txt | 27 self the average number of milliseconds spent in this
31 total the average number of milliseconds spent in this
68 the total amount of time spent in each function and its children.
80 % time This is the percentage of the `total' time that was spent
85 self This is the total amount of time spent in this function.
|
| D | profile2.txt | 35 self the average number of milliseconds spent in this
39 total the average number of milliseconds spent in this
115 the total amount of time spent in each function and its children.
127 % time This is the percentage of the `total' time that was spent
132 self This is the total amount of time spent in this function.
|
| /third_party/flutter/flutter/packages/flutter/lib/src/rendering/ |
| D | performance_overlay.dart | 18 /// This is the time spent by the rasterizer as it tries
26 /// time spent by the rasterizer as a fraction of the total frame slice. When
40 /// spent by the engine as a fraction of the total frame slice. When the bar
|
| /third_party/skia/third_party/externals/opengl-registry/extensions/I3D/ |
| D | WGL_I3D_swap_frame_usage.txt | 38 The value, percent, indicates the amount of time spent during the
88 that represents the percentage of time that the application spent
89 drawing a scene. The percentage is calculated as the time spent
|
| /third_party/openGLES/extensions/I3D/ |
| D | WGL_I3D_swap_frame_usage.txt | 38 The value, percent, indicates the amount of time spent during the
88 that represents the percentage of time that the application spent
89 drawing a scene. The percentage is calculated as the time spent
|
| /third_party/curl/src/ |
| D | tool_progress.c | 188 curl_off_t spent = tvdiff(now, *start)/1000; in progress_meter() local
282 time2str(time_spent, spent); in progress_meter()
|
| /third_party/mesa3d/docs/drivers/openswr/ |
| D | profiling.rst | 17 hierarchical breakdown of the time spent in the various operations.
|
| /third_party/skia/third_party/externals/oboe/apps/OboeTester/docs/ |
| D | AutomatedTesting.md | 161 unlocked.frames = 2528 # frames spent trying to lock onto the signal
162 locked.frames = 384084 # frames spent locked onto a good signal with no glitches
163 glitch.frames = 0 # frames spent glitching or recovering from a glitch
|
| /third_party/skia/third_party/externals/angle2/src/tests/test_utils/runner/ |
| D | README.md | 17 * `--batch-timeout` limits the amount of time spent in each batch
26 * `--test-timeout` limits the amount of time spent in each test
|
| /third_party/boost/libs/process/doc/ |
| D | acknowledgements.qbk | 3 …drafts since then. Especially Merino Vidal, Ilya Sokolov and Felipe Tanus spent a lot of time work…
|
| /third_party/typescript/tests/baselines/reference/tscWatch/watchEnvironment/watchFile/ |
| D | using-dynamic-priority-polling.js | 52 Change:: Time spent to Transition libFile and file1 to low priority queue
|
| /third_party/flutter/flutter/packages/flutter_driver/lib/src/driver/ |
| D | timeline_summary.dart | 28 /// Average amount of time spent per frame in the framework building widgets,
56 /// Average amount of time spent per frame in the GPU rasterizer.
|
| /third_party/toybox/kconfig/ |
| D | README | 18 than the author of squashfs, who spent 5 years actively trying to get his code
|
| /third_party/curl/docs/ |
| D | PARALLEL-TRANSFERS.md | 28 o current time the transfers have spent so far
|
| /third_party/mesa3d/src/freedreno/ci/ |
| D | freedreno-a530-skips.txt | 18 # Takes more than a few minutes, time is spent in batch_draw_tracking().
|
| D | freedreno-a630-skips.txt | 26 # Still running after 3 hours, time is spent in batch_draw_tracking().
|
| /third_party/python/Doc/library/ |
| D | profile.rst | 91 for the total time spent in the given function (and excluding time made in
98 is the cumulative time spent in this and all subfunctions (from invocation
173 to sort according to time spent within each function, and then print the
511 second non-parenthesized number repeats the cumulative time spent in the
516 cumulative times spent in the current function while it was invoked by
549 deduces where time is being spent. The latter technique traditionally involves
551 relative indications of where time is being spent.
|
| D | resource.rst | 296 has been used, e.g. amount of time spent running is user mode or number of times
304 floating point values representing the amount of time spent executing in user
305 mode and the amount of time spent executing in system mode, respectively. The
|
| /third_party/boost/more/getting_started/detail/ |
| D | build-from-source-tail.rst | 18 In particular, to limit the amount of time spent building, you may
|
| /third_party/libunwind/doc/ |
| D | libunwind-setjmp.tex | 35 system-provided routines. In fact, the time spent on a
|
123456