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

12 3 4 5 6 7 8 91011>>

  /external/autotest/client/site_tests/platform_CompressedSwapPerf/
control 2 PURPOSE = "Measure performance of compressed swap."
13 Run some basic performance benchmarks on compressed swap.
  /external/icu/icu4j/perf-tests/
README.txt 3 README for ICU4J Performance Test
5 Please note that to run the performance test for ICU4J as a part of continuous build, you will need to setup Perl with the following modules:
manifest.stub 2 Specification-Title: ICU for Java Performance Tests
5 Implementation-Title: ICU for Java Performance Tests
  /external/chromium-trace/catapult/
README.md 9 Catapult is the home for several performance tools that span from gathering,
10 displaying and analyzing performance data. This includes:
13 * [Performance Insights](/perf_insights/README.md)
15 * [Performance Dashboard](/dashboard/README.md)
17 These tools were created by Chromium developers for performance analysis,
  /external/eclipse-basebuilder/basebuilder-3.6.2/org.eclipse.releng.basebuilder/plugins/org.eclipse.test.performance.ui/
contexts.xml 3 <description>This view shows the performance results in a hierarchical tree:
8 + Performance numbers
10 Typically, the Eclipse builder runs performance tests for each component after the build is made on several performance test machines. Each component defines one or several specific performance test suites made of several test (aka scenario). Several performance numbers (e.g. Elapsed Process Time and CPU Time) are stored for each scenario and all build results are available in the performance results database.
12 This structure is roughly the same than the one used to generate performance results, hence make it easy to match the numbers in the corresponding page HTML page.</description>
23 <description>This view show for each of the performance machine the entire results since the beginning.
25 Each tab of this view represent a performance machine (also named config)
    [all...]
performanceui.jar 
plugin.xml 11 class="org.eclipse.test.performance.ui.Main">
18 class="org.eclipse.test.internal.performance.results.ui.PerformanceResultsPreferencePage"
19 id="org.eclipse.test.performance.ui.prpp"
32 class="org.eclipse.test.internal.performance.results.ui.ComponentsView"
34 id="org.eclipse.test.internal.performance.results.ui.ComponentsView"
39 class="org.eclipse.test.internal.performance.results.ui.BuildsView"
41 id="org.eclipse.test.internal.performance.results.ui.BuildsView"
46 class="org.eclipse.test.internal.performance.results.ui.ComponentResultsView"
48 id="org.eclipse.test.internal.performance.results.ui.ComponentsResultsView"
56 class="org.eclipse.test.internal.performance.results.ui.PerformanceResultsPreferenceInitializer"
    [all...]
  /development/testrunner/tests/
am_instrument_parser_tests.py 27 result="""INSTRUMENTATION_RESULT: performance.java_size=4871
30 INSTRUMENTATION_RESULT: performance.cpu_time=33846
51 INSTRUMENTATION_STATUS: performance.cpu_time=866
52 INSTRUMENTATION_STATUS: performance.execution_time=1242
68 INSTRUMENTATION_STATUS: performance.cpu_time=590
69 INSTRUMENTATION_STATUS: performance.execution_time=1122
129 INSTRUMENTATION_STATUS: performance.cpu_time=866
130 INSTRUMENTATION_STATUS: performance.execution_time=1242
145 INSTRUMENTATION_STATUS: performance.cpu_time=590
146 INSTRUMENTATION_STATUS: performance.execution_time=112
    [all...]
  /external/eclipse-basebuilder/basebuilder-3.6.2/org.eclipse.releng.basebuilder/plugins/org.eclipse.test.performance.ui/META-INF/
MANIFEST.MF 4 Bundle-SymbolicName: org.eclipse.test.performance.ui; singleton:=true
7 Bundle-Activator: org.eclipse.test.performance.ui.UiPlugin
15 org.eclipse.test.performance.derby;bundle-version="10.4.2";resolution:=optional,
18 org.eclipse.test.performance;bundle-version="3.6.0",
23 Export-Package: org.eclipse.test.internal.performance.results.db,
24 org.eclipse.test.internal.performance.results.model,
25 org.eclipse.test.internal.performance.results.ui,
26 org.eclipse.test.internal.performance.results.utils,
27 org.eclipse.test.performance.ui
  /external/autotest/client/site_tests/hardware_StorageTrim/
control 7 PURPOSE = 'Measure write performance before and after trim. (for SSD)'
14 Measure write performance. Trim all the disk. Measure write performance.
control.mmc 7 PURPOSE = 'Measure write performance before and after trim. (for eMMC)'
14 Measure write performance. Trim all the disk. Measure write performance.
  /external/chromium-trace/catapult/telemetry/telemetry/util/
__init__.py 4 """A library for bootstrapping Telemetry performance testing."""
  /frameworks/base/docs/html/training/
best-performance.jd 1 page.title=Best Practices for Performance
  /toolchain/binutils/binutils-2.25/gas/testsuite/gas/mips/
perfcount.s 1 # source file to test assembly of R1[20]000 performance counter instructions.
  /external/v8/
ChangeLog 3 Performance and stability improvements on all platforms.
8 Performance and stability improvements on all platforms.
13 Performance and stability improvements on all platforms.
18 Performance and stability improvements on all platforms.
23 Performance and stability improvements on all platforms.
28 Performance and stability improvements on all platforms.
33 Performance and stability improvements on all platforms.
38 Performance and stability improvements on all platforms.
43 Performance and stability improvements on all platforms.
48 Performance and stability improvements on all platforms
    [all...]
  /external/autotest/client/site_tests/platform_Pkcs11LoadPerf/
control 8 TEST_CATEGORY = "Performance"
13 This tests the performance of loading a PKCS #11 token.
  /external/autotest/client/tests/parallel_dd/
control 4 TEST_CATEGORY = "PERFORMANCE"
8 Measures the performance of writing and reading multiple streams of files onto
  /external/chromium-trace/catapult/perf_insights/
README.md 5 This folder contains code for http://performance-insights.appspot.com/,
7 order to understand performance issues in Chrome, at scale
  /external/eclipse-basebuilder/basebuilder-3.6.2/org.eclipse.releng.basebuilder/plugins/org.eclipse.test.performance.ui/html/
overview.html 11 The performance results tool provide an easy way to look at results collected
12 while running performance tests on a build. It is accessible using the <b>Performance Results</b>
14 <p><img src="images/perspective.png" alt="Performance Results perspective"/></p>
28 The goal of this tool is both to look at performance results database numbers
29 and to verify whether a build result may have scenario showing performance regression.
31 The view to use to look at performance results number is the <a href="components.html">Components view</a>.
34 <a href="http://download.eclipse.org/eclipse/downloads/drops/R-3.5-200906111540/performance/performance.php">Eclipse 3.5.0</a>).
35 The complete performance results information is provided on each element of the tree in th
    [all...]
  /frameworks/base/docs/html/topic/performance/
index.jd 1 page.title=Performance
3 page.metaDescription=Improve your app's performance by learning how to optimize power consumption, launch times, and other important areas of performance.
5 meta.tags="performance"
6 page.tags="performance"
13 but it's just the beginning. The next step is maximizing your app's performance.
32 data-query="collection:develop/performance/landing"
  /external/autotest/client/site_tests/graphics_PerfControl/
control 16 TEST_CATEGORY = 'Performance'
17 TEST_CLASS = "Performance"
25 Performance tests should be wrapped in a PerfControl object to ensure
26 consistent thermal state and performance results. This test exercises
27 this basic functionality with a Noop performance test.
  /external/autotest/client/site_tests/video_WebRtcPerf/
control 8 CRITERIA = "This is a performance test and does not fail."
12 TEST_CATEGORY = "Performance"
22 hardware acceleration to the performance dashboard. The test runs on all the
23 devices. The output can be used to compare the performance between using
24 hardware and software. It can also be used to compare the performance among
  /external/icu/icu4c/source/test/perf/DateFmtPerf/
ReadMe.txt 8 The purpose of this performance test is to test the "real world" applications of ICU, such as Date Formatting and the Break Iterator. In both of these cases, the performance test function does all of the work, i.e. initializing, formatting, etc.
10 There is no Perl script associated with this performance test, due to the fact that the performance test results in a different time if it is allowed to run more than once per execution of the executable. We are only interested in the first time returned by the executable in order to maintain accurate "real world" results. For this to happen, make sure to run the executable with the -i 1 and -p 1 options.
12 There are 7 tests contained in this performance test:
  /external/autotest/client/site_tests/graphics_WebGLPerformance/
control 7 PURPOSE = "Execute the WebGL performance test suite."
12 TEST_CATEGORY = "Performance"
20 This test runs the WebGL performance tests.
  /external/chromium-trace/catapult/dashboard/
README.md 0 # Performance Dashboard
3 The Chrome Performance Dashboard is a App Engine web app for displaying
4 and monitoring performance test results.

Completed in 1382 milliseconds

12 3 4 5 6 7 8 91011>>