HomeSort by relevance Sort by last modified time
    Searched full:performance (Results 426 - 450 of 6790) sorted by null

<<11121314151617181920>>

  /external/opencv3/doc/py_tutorials/py_core/py_optimization/
py_optimization.markdown 0 Performance Measurement and Improvement Techniques {#tutorial_py_optimization}
11 - To measure the performance of your code.
12 - Some tips to improve the performance of your code.
21 Measuring Performance with OpenCV
83 Measuring Performance in IPython
86 Sometimes you may need to compare the performance of two similar operations. IPython gives you a
118 We will try one more example. This time, we will compare the performance of **cv2.countNonZero()**
137 There are several other magic commands to measure the performance, profiling, line profiling, memory
141 Performance Optimization Techniques
144 There are several techniques and coding methods to exploit maximum performance of Python and Numpy
    [all...]
  /external/owasp/sanitizer/tools/findbugs/doc/
performance.html 3 <title>FindBugs Performance Improvements and Regressions</title>
58 <h1>FindBugs Performance Improvements and Regressions</h1> I did a performance check against 179
60 benchmarks), FindBugs 2.0 gives a 9% performance improvement over 1.3.9. 154 of the 179 benchmarks saw
61 performance improvements; 24 saw regressions. All of the benchmarks that saw regressions of more than
64 a look, and couldn't find anything that stood out as being a performance glitch in FindBugs. I haven't
69 <p> If you are seeing any significant performance regressions in FindBugs 2.0,
  /external/pcre/dist/doc/
pcreperform.3 4 .SH "PCRE PERFORMANCE"
7 Two aspects of performance are discussed below: memory usage and processing
90 about optimizing regular expressions for efficient performance. This document
100 backwards compatibility, and partly for performance reasons. However, you can
103 a traditional matching function; the performance loss is less with
123 newlines, the best performance is obtained by setting PCRE_DOTALL, or starting
157 In many cases, the solution to this kind of performance issue is to use an
  /external/squashfs-tools/RELEASE-READMEs/
README-3.1 20 This significantly speeds up performance on SMP systems.
23 threads to maximise I/O performance. Even on single processor systems
24 this speeds up performance by at least 10%.
34 5. The use of swap memory was found to significantly impact performance. The
61 1.2 PERFORMANCE RESULTS
124 I'll be interested in any performance results obtained, especially from SMP
127 deadlocks, low performance etc.
  /frameworks/rs/driver/runtime/
rs_structs.h 20 * potential runtime performance penalties for tight loops operating on
99 * potential runtime performance penalties for tight loops operating on
133 * potential runtime performance penalties for tight loops operating on
162 * potential runtime performance penalties for tight loops operating on
198 * potential runtime performance penalties for tight loops operating on
240 * potential runtime performance penalties for tight loops operating on
283 * potential runtime performance penalties for tight loops operating on
  /external/eclipse-basebuilder/basebuilder-3.6.2/org.eclipse.releng.basebuilder/plugins/org.eclipse.test.performance.ui/src/org/eclipse/test/performance/ui/
ScenarioStatusTable.java 11 package org.eclipse.test.performance.ui;
17 import org.eclipse.test.internal.performance.results.db.BuildResults;
18 import org.eclipse.test.internal.performance.results.db.ConfigResults;
19 import org.eclipse.test.internal.performance.results.db.PerformanceResults;
20 import org.eclipse.test.internal.performance.results.db.ScenarioResults;
194 this.stream.print("The following table gives a complete but compact view of performance results for the component.<br>\n");
205 this.stream.print("\">): mark a <b>successful result</b>, which means this test has neither significant performance regression nor significant standard error</li>");
208 this.stream.print("\">): mark a <b>failing result</b>, which means this test shows a significant performance regression (more than 10%)</li>\n");
222 this.stream.print("<li>\"n/a\": mark a test for with <b>no</b> performance results</li>\n");
  /frameworks/base/docs/html/training/improving-layouts/
optimizing-layout.jd 2 parent.title=Improving Layout Performance
58 bottlenecks in the layout performance.</p>
62 Layout and Draw performance, helping you identify potential issues.</p>
67 times&mdash;such as this one&mdash;are optimized as the performance
88 performance times.</p>
106 <p>Because the layout performance above slows down due to a nested {@link
107 android.widget.LinearLayout}, the performance might improve by flattening the layout&mdash;make
145 <li>Deep layouts - Layouts with too much nesting are bad for performance. Consider using flatter layouts such as {@link android.widget.RelativeLayout} or {@link android.widget.GridLayout} to improve performance. The default maximum depth is 10.</li>
  /external/autotest/client/common_lib/perf_expectations/
expectation_checker.py 5 """Automated performance regression detection tool for ChromeOS perf tests.
31 """Check performance results against expectations."""
37 @param test_name: the name of the performance test,
88 """Compare a performance value of a trace with the expectation.
91 @param trace_perf_value: the performance value of the trace.
  /external/crcalc/
impl.html 15 and to provide the best possible performance. To do so would have
22 performance for all operations.
23 <LI> Use algorithms with asymptotically reasonable performance.
42 function. In order to obtain reasonable performance, each object
98 The issues related to using this in a higher performance implementation
  /external/deqp/doc/testspecs/GLES2/
performance.shaders.operator.txt 19 Shader operator performance tests
22 + dEQP-GLES2.performance.shaders.operator.*
31 - Covered in performance.texture.
72 See performance.txt for more details on shader performance testing.
  /external/deqp/doc/testspecs/GLES3/
performance.shaders.operator.txt 19 Shader operator performance tests
22 + dEQP-GLES3.performance.shaders.operator.*
31 - Covered in performance.texture.
76 See performance.txt for more details on shader performance testing.
  /external/libchrome/base/synchronization/
condition_variable.h 36 // called Wait(). This results in POOR performance. A much better
43 // done, and leaves no sleeping threads... and performance is less
54 // This implementation offers support for "performance" in its selection of
55 // which thread to revive. Performance, in direct contrast with "fairness,"
59 // may improve performance, as the selected thread may have a greater chance of
  /packages/apps/UnifiedEmail/src/com/android/mail/perf/
Timer.java 30 * Performance timing utilities for Gmail.
32 * There are two main ways to log performance. For simple, one off events, the static methods
63 // Set to true to enable logging of performance stats.
66 /** An internal structure used for performance markers. */
205 * consisted of {@code numSubIterations} sub-events, so that performance output will be denoted
  /art/runtime/
compiler_filter.h 40 kBalanced, // Good performance return on compilation investment.
41 kSpeedProfile, // Maximize runtime performance based on profile.
42 kSpeed, // Maximize runtime performance.
  /external/autotest/server/site_tests/audio_AudioBasicHDMI/
audio_AudioBasicHDMI.py 38 """Set the CPU scaling governor mode to performance mode."""
40 0, 'performance')
41 logging.debug('Set CPU0 scaling governor mode to performance, '
  /external/chromium-trace/catapult/systrace/profile_chrome/
chrome_controller.py 32 re.compile(r'Logging performance trace to file')
48 raise RuntimeError('Performance trace category list marker not found. '
79 # 1. "Logging performance trace to file"
  /external/chromium-trace/catapult/tracing/third_party/css-element-queries/
README.md 6 size while not causing performance lags due to event based implementation.
12 - no performance issues since it listens only on size changes of elements that have element query rules defined through css. Other element query polifills only listen on `window.onresize` which causes performance issues and allows only to detect changes via window.resize event and not inside layout changes like css3 animation, :hover, DOM changes etc.
  /external/chromium-trace/catapult/tracing/tracing/base/
raf.html 46 var delta = Date.now() - window.performance.now();
118 return rafCompletionDeadline - window.performance.now();
133 // window.performance.now() on some platforms from blocking the idle
task_test.html 96 var result = window.performance.getEntriesByName('Test:pushB');
124 var result = window.performance.getEntriesByName('Test:pushB');
165 var result = window.performance.getEntriesByName('Test:pushB');
  /external/eclipse-basebuilder/basebuilder-3.6.2/org.eclipse.releng.basebuilder/plugins/org.eclipse.build.tools/data/
builds-eclipse-3.3.xml 39 <test href="http://download.eclipse.org/eclipse/downloads/drops/I20060922-0010/performance/performance.php" type="performance">
  /external/libgdx/backends/gdx-backends-gwt/src/com/badlogic/gdx/backends/gwt/
GwtApplicationConfiguration.java 44 /** preserve the back buffer, needed if you fetch a screenshot via canvas#toDataUrl, may have performance impact **/
47 * effectively allows transparent backgrounds in GWT, at a performance cost. **/
49 /** whether to use premultipliedalpha, may have performance impact **/
  /external/libjpeg-turbo/java/
README 18 Performance Pitfalls
26 or to prevent performance degradation. Background garbage collection can kill
27 performance, particularly in a multi-threaded environment (Java pauses all
  /external/markdown/docs/
release-2.0.txt 6 extending the extension API, increased performance, and added numerous
40 notable increases in performance.
46 The core parser had been completely rewritten, increasing performance and, for
  /external/skia/site/user/quick/
desktop.md 69 Performance tests
72 Build and run nanobench (performance tests). In this case, we will
74 performance tests.
  /libcore/ojluni/src/main/java/java/util/
RandomAccess.java 32 * behavior to provide good performance when applied to either random or
40 * provide poor performance if it were applied to a sequential access list,
42 * performance.

Completed in 1915 milliseconds

<<11121314151617181920>>