| /external/perfetto/docs/contributing/ |
| D | perfetto-in-the-press.md | 7 - [Performance: Perfetto Traceviewer - MAD Skills](https://www.youtube.com/watch?v=phhLFicMacY) 8 "On this episode of the MAD Skills series on Performance, Android Performance Engineer Carmen Jacks… 9 - [Performance and optimisation on the Meta Quest Platform](https://m.facebook.com/RealityLabs/vide… 10 - [Performance testing through proportional traces 11 ](https://www.jviotti.com/2022/09/07/performance-testing-through-proportional-traces.html) 12 …Performance](https://www.twoscomplement.org/podcast/performance.mp3) An episode of the [Twoscomple… 15 difficult to find the root cause of performance problems. By leveraging traces, 20 to performance tests and finally in production." 21 …performance](https://devblogs.microsoft.com/performance-diagnostics/perfetto-tooling-for-analyzing…
|
| /external/squashfs-tools/RELEASE-READMEs/ |
| D | PERFORMANCE.README | 1 GENERAL INFORMATION ON PERFORMANCE TESTS 4 The following performance tests were based on two file sets: the 7 The Ubuntu liveCD filesystem was used to test filesystem performance 9 CRAMFS filesystem performance could not be tested for this filesystem 11 CRAMFS performance against Squashfs, the liveCD filesystem from 20 1. Ubuntu liveCD performance tests 28 1.1 Performance tests from CDROM 30 1.1.1 Directory Lookup performance 40 1.1.2 Sequential I/O performance 50 1.1.3 Random I/O performance [all …]
|
| /external/mesa3d/src/intel/compiler/ |
| D | brw_ir_performance.h | 34 * Various estimates of the performance of a shader based on static 37 struct performance { struct 38 performance(const fs_visitor *v); 39 performance(const vec4_visitor *v); 40 ~performance(); 73 * performance doesn't scale without limits as a function of its thread argument 80 performance(const performance &perf); argument 81 performance & 82 operator=(performance u); argument
|
| /external/tensorflow/tensorflow/lite/g3doc/examples/build/ |
| D | index.md | 51 For more information building effective, compatible, high performance models 53 [Performance best practices](../../performance/best_practices). 77 Whether you are looking to benchmark performance for a 94 Once you've developed your model, you should evaluate its performance and test 103 * [Benchmarking tools](https://www.tensorflow.org/lite/performance/measurement) 106 for important performance metrics. 112 model performance well and uses less compute resources. Machine learning model 113 performance is usually a balance between size and speed of inference vs 116 [model optimization] (https://www.tensorflow.org/lite/performance/model_optimization) 133 [performance best practices guide](https://www.tensorflow.org/lite/performance/best_practices) [all …]
|
| /external/cronet/third_party/icu/source/test/perf/ |
| D | README | 7 README for ICU4C Performance Test 10 The performance tests in ICU4C compares various aspects of ICU against previous versions of ICU, 12 performance tests are driven by a perl-based script which calls the underlying C program and 26 Running Performance Test: 33 3) Build the ICU performance tests either through Visual Studios or with the Makefile. 34 (The location of the performance test is: icu/source/test/perf) 39 b) Path to the performance test data 57 Note: After building the performance tests, it is a good idea to execute each C program to ensure t… 59 Note: To run the actual performance test, you will need to setup Perl with the following modules: 62 …s take a while depending on the machine it is running on so a script to run each performance test's
|
| /external/icu/icu4c/source/test/perf/ |
| D | README | 7 README for ICU4C Performance Test 10 The performance tests in ICU4C compares various aspects of ICU against previous versions of ICU, 12 performance tests are driven by a perl-based script which calls the underlying C program and 26 Running Performance Test: 33 3) Build the ICU performance tests either through Visual Studios or with the Makefile. 34 (The location of the performance test is: icu/source/test/perf) 39 b) Path to the performance test data 57 Note: After building the performance tests, it is a good idea to execute each C program to ensure t… 59 Note: To run the actual performance test, you will need to setup Perl with the following modules: 62 …s take a while depending on the machine it is running on so a script to run each performance test's
|
| /external/deqp/doc/testspecs/GLES2/ |
| D | performance.txt | 19 Performance tests 22 in performance test cases. 25 Measuring performance: 27 Performance test cases must satisfy following conditions: 29 + Result should represent the performance of the tested feature or use case. 45 performance is expected to vary between iterations (due to undeterministic 48 the performance is more important from user experience perspective. 75 * Minimum and maximum computed performance 76 * Average computed performance 81 Shader execution tests measure the performance of single pair of vertex and [all …]
|
| D | performance.texture.format.txt | 19 Texture format performance tests 22 + dEQP-GLES2.performance.texture.format.* 25 + Texture lookup performance with all uncompressed texture formats 31 + Performance of other filtering or wrap modes 32 - Covered performance.texture.filtering and performance.texture.wrap 36 Test cases measure performance of 2D and cubemap texture lookups without 56 See performance.txt for more details on shader performance testing.
|
| /external/deqp/doc/testspecs/GLES3/ |
| D | performance.txt | 19 Performance tests 22 in performance test cases. 25 Measuring performance: 27 Performance test cases must satisfy following conditions: 29 + Result should represent the performance of the tested feature or use case. 45 performance is expected to vary between iterations (due to undeterministic 48 the performance is more important from user experience perspective. 75 * Minimum and maximum computed performance 76 * Average computed performance 81 Shader execution tests measure the performance of single pair of vertex and [all …]
|
| D | performance.buffer.data_upload.txt | 19 Buffer upload performance tests 22 + dEQP-GLES3.performance.buffer.data_upload.* 25 + Memcpy performance tests for reference values 26 + Performance of glBufferData and glBufferSubData 40 + Buffer mapping performance 61 + Buffer upload performance after a draw call using the target buffer 64 + Uploaded buffer rendering performance tests 69 + Sustained upload performance tests 73 Upload performance tests approximate upload speed by testing time usage of different 101 reference value. "small_buffers" test case tests memcpy performance with transfer size [all …]
|
| /external/tensorflow/tensorflow/compiler/xla/mlir_hlo/ |
| D | .clang-tidy | 38 performance-for-range-copy, 39 performance-implicit-conversion-in-loop, 40 performance-inefficient-algorithm, 41 performance-inefficient-vector-operation, 42 performance-move-const-arg, 43 performance-no-automatic-move, 44 performance-trivially-destructible, 45 performance-unnecessary-copy-initialization, 46 performance-unnecessary-value-param,
|
| /external/tensorflow/tensorflow/compiler/mlir/lite/quantization/ir/ |
| D | .clang-tidy | 37 performance-for-range-copy, 38 performance-implicit-conversion-in-loop, 39 performance-inefficient-algorithm, 40 performance-inefficient-vector-operation, 41 performance-move-const-arg, 42 performance-no-automatic-move, 43 performance-trivially-destructible, 44 performance-unnecessary-copy-initialization, 45 performance-unnecessary-value-param,
|
| /external/python/google-api-python-client/docs/dyn/ |
| D | monitoring_v3.services.serviceLevelObjectives.html | 113 …esired good service. It consists of a service-level indicator (SLI), a performance goal, and a per… 119 …performance" of a service. For some services, the SLI is well-defined. In such cases, the SLI… 120 …"basicSli": { # An SLI measuring performance on a well-known service type. Performance w… 126 …relevant. Telemetry from other locations will not be used to calculate performance for this SLI. I… 129 …s relevant. Telemetry from other methods will not be used to calculate performance for this SLI. I… 132 …evant. Telemetry from other API versions will not be used to calculate performance for this SLI. I… 152 …w is good when that window has a sufficiently high performance. # A window is good if its performa… 153 …t;basicSliPerformance": { # An SLI measuring performance on a well-known service type. Perfor… 159 …relevant. Telemetry from other locations will not be used to calculate performance for this SLI. I… 162 …s relevant. Telemetry from other methods will not be used to calculate performance for this SLI. I… [all …]
|
| /external/autotest/server/site_tests/network_WiFi_AssocConfigPerformance/ |
| D | network_WiFi_AssocConfigPerformance.py | 15 """Test for performance of discovery, association, and configuration, and 17 Measure and report the performance of the suspend/resume cycle. 32 """Output a summary of performance to logs and to perf value json 34 @param descript: string description of the performance numbers, 81 WiFi connection, and report the performance of that resume. 124 # Measure performance for each HostapConfig 126 # need to track the performance numbers for each operation 139 # process reported performance to group the numbers by step 144 # report the performance from the connect_disconnect 159 # process reported performance to group the numbers by step [all …]
|
| /external/grpc-grpc/tools/internal_ci/linux/ |
| D | grpc_full_performance_master.sh | 27 …--remote_worker_host grpc-kokoro-performance-server-8core grpc-kokoro-performance-client-8core grp… 41 …--remote_worker_host grpc-kokoro-performance-server-32core grpc-kokoro-performance-client-32core g… 54 --remote_worker_host grpc-kokoro-performance-windows1 grpc-kokoro-performance-windows2 \
|
| D | grpc_full_performance_release.sh | 27 …--remote_worker_host grpc-kokoro-performance-server-8core grpc-kokoro-performance-client-8core grp… 41 …--remote_worker_host grpc-kokoro-performance-server-32core grpc-kokoro-performance-client-32core g… 54 --remote_worker_host grpc-kokoro-performance-windows1 grpc-kokoro-performance-windows2 \
|
| /external/tensorflow/tensorflow/lite/g3doc/ |
| D | _book.yaml | 56 path: /lite/performance/delegates 58 path: /lite/performance/gpu 60 path: /lite/performance/gpu_advanced 62 path: /lite/performance/implementing_delegate 167 path: /lite/performance/coreml_delegate 244 - title: "Performance best practices" 245 path: /lite/performance/best_practices 246 - title: "Performance measurement" 247 path: /lite/performance/measurement 285 path: /lite/performance/model_optimization [all …]
|
| /external/tensorflow/tensorflow/lite/g3doc/guide/ |
| D | index.md | 18 - *High performance*, with [hardware acceleration](../performance/delegates) 19 and [model optimization](../performance/model_optimization). 34 Note: Refer to the [performance best practices](../performance/best_practices) 35 guide for an ideal balance of performance, model size, and accuracy. 66 [optimizations](../performance/model_optimization) such as 67 [quantization](../performance/post_training_quantization) to reduce model 93 On Android and iOS devices, you can improve performance using hardware 95 [GPU Delegate](../performance/gpu), on android you can either use the 98 iOS you can use the [Core ML Delegate](../performance/coreml_delegate). To add 100 [define your own delegate](../performance/implementing_delegate).
|
| /external/deqp/modules/gles3/performance/ |
| D | es3pPerformanceTests.cpp | 21 * \brief Performance tests. 44 namespace Performance namespace 53 : TestCaseGroup(context, "texture", "Texture Performance Tests") in TextureTestGroup() 71 : TestCaseGroup(context, "shader", "Shader Performance Tests") in ShadersTestGroup() 88 : TestCaseGroup(context, "api", "API Performance Tests") in APITests() 106 : TestCaseGroup(context, "buffer", "Buffer Performance Tests") in BufferTestGroup() 119 : TestCaseGroup(context, "performance", "Performance Tests") in PerformanceTests() 138 } // Performance
|
| /external/pigweed/pw_perf_test/ |
| D | docs.rst | 6 Pigweed's perf test module provides an easy way to measure performance on 18 The user experience of writing a performance test is intended to be as 20 code, writing a performance test is as easy as: 51 // The State object is injected into a performance test by including it as an 68 Registers a performance test. Any additional arguments are passed to the test 73 Like the original PW_PERF_TEST macro it registers a performance test. However 80 // Declare performance test functions. 126 The performance testing framework relies heavily on the member functions of 133 Handles events from a performance test. 145 Called when a new performance test is started [all …]
|
| /external/autotest/server/cros/network/ |
| D | perf_test_manager.py | 13 """These are the different performance test types that are supported by 15 example 'tcp_rx' refers to a performance test of data transfer from a remote 27 """Manager for Performance tests. This class provides a unified API to allow 28 callers run performance tests using the supported tools. 47 """Get a config object for a performance tests based on the test 74 """Get a Session object for a set of performance tests. Will return 79 @param peer_device_proxy: LinuxSystem object for the performance testing 123 """Get a single performance result from a list of results. 139 """Convert a performance test type to a netperf test type. 161 """Convert a performance test type to an iperf test type
|
| /external/rust/crates/vulkano/src/instance/ |
| D | debug.rs | 14 //! invalid API usages or performance problems by calling this callback. The callback can also 17 //! Note that the vulkano library can also emit messages to warn you about performance issues. 122 performance: !(ty & ash::vk::DebugUtilsMessageTypeFlagsEXT::PERFORMANCE) in new() 163 if ty.performance { in new() 164 flags |= ash::vk::DebugUtilsMessageTypeFlagsEXT::PERFORMANCE; in new() 348 pub performance: bool, field 358 performance: false, in general() 368 performance: false, in validation() 372 /// Builds a `MessageType` with performance field set to `true`. 374 pub const fn performance() -> MessageType { in performance() method [all …]
|
| /external/tensorflow/tensorflow/core/profiler/protobuf/ |
| D | overview_page.proto | 39 // Remark text in the performance summary section. 70 // Overview result for a performance tip to users. 77 // Indicates if kernel launch is a performance bottleneck. Possible values: 81 // performance. 83 // Indicates if all other is a performance bottleneck. Possible values: "no", 87 // performance. 92 // Indicates if device collectives are a performance bottleneck. Possible 96 // device-collectives performance. 102 // Possible performance bottleneck: "host", "device", "both". 122 // A list of tips for improving host performance. [all …]
|
| /external/deqp/modules/gles2/performance/ |
| D | es2pPerformanceTests.cpp | 21 * \brief Performance tests. 44 namespace Performance namespace 53 : TestCaseGroup(context, "texture", "Texture Performance Tests") in TextureTestGroup() 72 : TestCaseGroup(context, "shader", "Shader Performance Tests") in ShadersTestGroup() 89 : TestCaseGroup(context, "api", "API Performance Tests") in APITestGroup() 105 : TestCaseGroup(context, "performance", "Performance Tests") in PerformanceTests() 122 } // Performance
|
| /external/tensorflow/tensorflow/lite/g3doc/performance/ |
| D | best_practices.md | 1 # Performance best practices 6 Lite model performance. 17  37 help in understanding performance bottlenecks and which operators dominate the 74 Multi-threaded execution, however, comes at the cost of increased performance 78 it may result in worse performance than single-threaded. 85 sure to carefully check the documentation for performance caveats. For example, 95 the performance bug may be not in the model but in parts of application code 133 The TensorFlow team is happy to help diagnose and address specific performance
|