• Home
  • History
  • Annotate
  • only in /external/icu/icu4c/source/test/perf/

..12-Mar-20154 KiB

charperf/12-Mar-20154 KiB

collationperf/12-Mar-20154 KiB

collperf/12-Mar-20154 KiB

collperf2/12-Mar-20154 KiB

convperf/12-Mar-20154 KiB

DateFmtPerf/12-Mar-20154 KiB

dicttrieperf/12-Mar-20154 KiB

howExpensiveIs/12-Mar-20154 KiB

icuperf2report.xsl12-Mar-20151.1 KiB

leperf/12-Mar-20154 KiB

Makefile.in12-Mar-20152.4 KiB

normperf/12-Mar-20154 KiB

perldriver/12-Mar-20154 KiB

README12-Mar-20152.9 KiB

strsrchperf/12-Mar-20154 KiB

ubrkperf/12-Mar-20154 KiB

ucnvavailperf/12-Mar-20154 KiB

unisetperf/12-Mar-20154 KiB

usetperf/12-Mar-20154 KiB

ustrperf/12-Mar-20154 KiB

utfperf/12-Mar-20154 KiB

utrie2perf/12-Mar-20154 KiB


1Copyright (C) 2008-2013, International Business Machines
2Corporation and others.  All Rights Reserved.
4README for ICU4C Performance Test
7The performance tests in ICU4C compares various aspects of ICU against previous versions of ICU,
8Posix, and/or Windows.  Some tests only run on Windows and are labeled accordingly.All of the 
9performance tests are driven by a perl-based script which calls the underlying C program and 
10displays the statistical analysis of the test in an easy to read HTML web page.  Each test will
11have its own web page.
15The most up to date tests are in ICU 4.0 and later. In addition, most tests depend on data which are 
16in a separate repository.
18Data repository:
20There are 3 folders in here: collation, conversion, and udr.
23Running Performance Test:
251) Checkout the current ICU and 2 previous versions (for proper regression testing) and the data
26   into your local system.
282) Do a general build on all the ICUs either through Visual Studios or with the Makefile.
303) Build the ICU performance tests either through Visual Studios or with the Makefile.
31   (The location of the performance test is: icu/source/test/perf)
334) Go to perf/perldriver, copy Common.pl.template to Common.pl.
34   In this file, you will need to set a few variables:
35   a) ICU version numbers
36   b) Path to the performance test data
37   c) Path to the root directory of the different versions of ICU
38   d) Whether or not you are running the test on Windows
39   * The Path needs to be absolute
40   * All other variables should be left as is
425) Create a directory pref/results. All of the test result web pages will be
43   stored in this directory.
456) In the perf directory, there are several other directories for the various tests that can be run.
46   (e.g. convperf (Conversion tests)). Go to each directory and execute the perl script for each test
47   you want to run. (e.g. CharPerf_r.pl in CharPerf directory)
48   * You only need to run the perl script from the latest ICU version.  The corresponding perl script 
49     in the previous versions of ICU do not need to be run seperately.
52Note: When running on Windows, cygwin is preferred.
53Note: If a test needs to be run on Windows, a message will be displayed.
54Note: After building the performance tests, it is a good idea to execute each C program to ensure that each
55      test can run. (e.g. convperf.exe)
56Note: To run the actual performance test, you will need to setup Perl with the following modules:
57      a) Statistics/Distribution.pm
58      b) Statistics/Descriptive.pm 
59Note: Some tests take a while depending on the machine it is running on so a script to run each performance test's
60      perl script might be helpful.
61Note: The perl script is only used in one version of ICU. When you run regression tests,
62      it is recommended to run the tests from the later version of ICU.