| /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/ |
| D | _book.yaml | 152 - heading: "Performance"
154 path: /lite/performance/best_practices
156 path: /lite/performance/measurement
158 path: /lite/performance/delegates
160 path: /lite/performance/gpu
162 path: /lite/performance/gpu_advanced
164 path: /lite/performance/nnapi
166 path: /lite/performance/hexagon_delegate
168 path: /lite/performance/coreml_delegate
170 path: /lite/performance/implementing_delegate
[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.
65 [optimizations](../performance/model_optimization) such as
66 [quantization](../performance/post_training_quantization) to reduce model
92 On Android and iOS devices, you can improve performance using hardware
94 [GPU Delegate](../performance/gpu), on android you can either use the
95 [NNAPI Delegate](../performance/nnapi) (for newer devices) or the
96 [Hexagon Delegate](../performance/hexagon_delegate) (on older devices) and on
[all …]
|
| /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/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/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/autotest/client/site_tests/longevity_Tracker/ |
| D | longevity_Tracker.py | 135 """Record attribute performance measurements, and write to file.
137 @param perf_values: dict of attribute performance values.
138 @param perf_writer: file to write performance measurements.
140 # Get performance measurements.
150 # Write performance measurements to perf timestamped file.
157 """Record 90th percentile metric of attribute performance values.
159 @param perf_values: dict attribute performance values.
160 @param perf_metrics: dict attribute 90%-ile performance metrics.
169 logging.info('== Performance values: %s', perf_values)
173 # Append 90th percentile to each attribute performance metric.
[all …]
|
| /external/autotest/server/site_tests/enterprise_LongevityTrackerServer/ |
| D | enterprise_LongevityTrackerServer.py | 40 Run Longevity Test: Collect performance data over long duration.
88 @param chart_data: performance results formatted as chart data.
146 @param perf_results: dict of attribute performance metrics.
160 @param perf_results: dict of attribute performance metrics.
176 Record attribute performance measurements, and write to file.
178 @param perf_values: dict of attribute performance values.
179 @param perf_writer: file to write performance measurements.
182 # Get performance measurements.
195 # Write performance measurements to perf timestamped file.
225 Track performance of Chrome OS over a long period of time.
[all …]
|
| D | enterprise_longevity_helper.py | 166 @param ts_file: file handle for performance timestamped file.
167 @param ag_file: file handle for performance aggregated file.
182 @param aggregated_fpath: file path to Aggregated performance values.
191 """Record 90th percentile metric of attribute performance values.
193 @param perf_values: dict attribute performance values.
194 @param perf_metrics: dict attribute 90%-ile performance metrics.
204 logging.info('Performance values: %s', perf_values)
208 # Append 90th percentile to each attribute performance metric.
216 Returns median of each attribute performance metric.
220 @param metrics: dict of attribute performance metric lists.
[all …]
|
| /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 | 14 """Test for performance of discovery, association, and configuration, and
16 Measure and report the performance of the suspend/resume cycle.
31 """Output a summary of performance to logs and to perf value json
33 @param descript: string description of the performance numbers,
80 WiFi connection, and report the performance of that resume.
123 # Measure performance for each HostapConfig
125 # need to track the performance numbers for each operation
138 # process reported performance to group the numbers by step
143 # report the performance from the connect_disconnect
158 # 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/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/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.
68 // Overview result for a performance tip to users.
75 // Indicates if kernel launch is a performance bottleneck. Possible values:
79 // performance.
81 // Indicates if all other is a performance bottleneck. Possible values: "no",
85 // performance.
90 // Indicates if device collectives are a performance bottleneck. Possible
94 // device-collectives performance.
100 // Possible performance bottleneck: "host", "device", "both".
120 // A list of tips for improving host performance.
[all …]
|
| /external/angle/src/tests/perf_tests/ |
| D | README.md | 1 # ANGLE Performance Tests
5 …wn dashboards. For example, a comparison of ANGLE's back-end draw call performance on Windows NVID…
19 …skip the driver entirely. These null configs are useful for diagnosing performance overhead in ANG…
46 * `--perf-counters`: Additional performance counters to include in the result output. Separate mult…
61 * [`UniformsBenchmark`](UniformsPerf.cpp): Tests performance of updating various uniforms counts fo…
67 * [`BindingsBenchmark`](BindingPerf.cpp): Tests Buffer binding performance. Does no draw call opera…
70 * [`TexSubImageBenchmark`](TexSubImage.cpp): Tests `glTexSubImage` update performance.
71 * [`BufferSubDataBenchmark`](BufferSubData.cpp): Tests `glBufferSubData` update performance.
72 * [`TextureSamplingBenchmark`](TextureSampling.cpp): Tests Texture sampling performance.
73 * [`TextureBenchmark`](TexturesPerf.cpp): Tests Texture state change 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/python/google-api-python-client/docs/ |
| D | performance.md | 1 # Performance Tips
3 …performance of your application. The documentation for the specific API you are using should have …
11 …ull representation of a resource after processing requests. For better performance, you can ask th…
21 …formatting options for the `fields` parameter, and you should see the "Performance Tips" page in t…
27 For more information about patch semantics, see the "Performance Tips" page in the documentation fo…
|
| /external/tensorflow/tensorflow/lite/g3doc/performance/ |
| D | best_practices.md | 1 # Performance best practices
6 Lite model performance.
17 ![Graph of model size vs accuracy](../images/performance/model_size_vs_accuracy.png "Model Size vs …
19 
38 help in understanding performance bottlenecks and which operators dominate the
75 Multi-threaded execution, however, comes at the cost of increased performance
79 it may result in worse performance than single-threaded.
86 sure to carefully check the documentation for performance caveats. For example,
96 the performance bug may be not in the model but in parts of application code
132 The TensorFlow team is happy to help diagnose and address specific performance
|
| D | measurement.md | 1 # Performance measurement
6 the following important performance metrics:
15 native command-line binaries, and they all share the same core performance
94 for more performance parameters that you could run with the benchmark app.
156 differences in performance relative to execution within an actual Android app.
161 Therefore, the Android benchmark app is preferred for performance measurement.
185 ### Native benchmark binary for multiple performance options in a single run
188 …ultiple performance options](https://github.com/tensorflow/tensorflow/tree/master/tensorflow/lite/…
190 that could only benchmark a single performance option at a time. They share the
196 A comma-separated list of TFLite performance options to benchmark.
[all …]
|
| /external/rust/crates/grpcio-sys/grpc/tools/internal_ci/linux/ |
| 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…
|