• Home
Name Date Size #Lines LOC

..--

DateFmtPerf/03-May-2024-1,7691,389

charperf/03-May-2024-1,016798

collationperf/03-May-2024-2,2181,698

collperf/03-May-2024-1,4751,178

collperf2/03-May-2024-2,3861,912

convperf/03-May-2024-4,5623,938

dicttrieperf/03-May-2024-806626

howExpensiveIs/03-May-2024-1,2971,062

leperf/03-May-2024-3,0742,111

normperf/03-May-2024-2,3952,006

perldriver/03-May-2024-1,144748

strsrchperf/03-May-2024-660534

ubrkperf/03-May-2024-2,1671,707

ucnvavailperf/03-May-2024-236167

unisetperf/03-May-2024-1,3781,039

usetperf/03-May-2024-718570

ustrperf/03-May-2024-1,4921,191

utfperf/03-May-2024-777623

utrie2perf/03-May-2024-647526

Makefile.inD03-May-20242.5 KiB9758

READMED03-May-20243 KiB6649

icuperf2report.xslD03-May-20241.3 KiB3424

perf.slnD03-May-202410.2 KiB148147

README

1Copyright (C) 2016 and later: Unicode, Inc. and others.
2License & terms of use: http://www.unicode.org/copyright.html#License
3
4Copyright (C) 2008-2013, International Business Machines
5Corporation and others.  All Rights Reserved.
6
7README for ICU4C Performance Test
8
9Introduction:
10The performance tests in ICU4C compares various aspects of ICU against previous versions of ICU,
11Posix, and/or Windows.  Some tests only run on Windows and are labeled accordingly.All of the
12performance tests are driven by a perl-based script which calls the underlying C program and
13displays the statistical analysis of the test in an easy to read HTML web page.  Each test will
14have its own web page.
15
16
17Requirements:
18The most up to date tests are in ICU 4.0 and later. In addition, most tests depend on data which are
19in a separate repository.
20
21Data repository:
22http://source.icu-project.org/repos/icu/data/trunk/test/perf
23There are 3 folders in here: collation, conversion, and udr.
24
25
26Running Performance Test:
27
281) Checkout the current ICU and 2 previous versions (for proper regression testing) and the data
29   into your local system.
30
312) Do a general build on all the ICUs either through Visual Studios or with the Makefile.
32
333) 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)
35
364) Go to perf/perldriver, copy Common.pl.template to Common.pl.
37   In this file, you will need to set a few variables:
38   a) ICU version numbers
39   b) Path to the performance test data
40   c) Path to the root directory of the different versions of ICU
41   d) Whether or not you are running the test on Windows
42   * The Path needs to be absolute
43   * All other variables should be left as is
44
455) Create a directory pref/results. All of the test result web pages will be
46   stored in this directory.
47
486) In the perf directory, there are several other directories for the various tests that can be run.
49   (e.g. convperf (Conversion tests)). Go to each directory and execute the perl script for each test
50   you want to run. (e.g. CharPerf_r.pl in CharPerf directory)
51   * You only need to run the perl script from the latest ICU version.  The corresponding perl script
52     in the previous versions of ICU do not need to be run seperately.
53
54
55Note: When running on Windows, cygwin is preferred.
56Note: If a test needs to be run on Windows, a message will be displayed.
57Note: After building the performance tests, it is a good idea to execute each C program to ensure that each
58      test can run. (e.g. convperf.exe)
59Note: To run the actual performance test, you will need to setup Perl with the following modules:
60      a) Statistics/Distribution.pm
61      b) Statistics/Descriptive.pm
62Note: Some tests take a while depending on the machine it is running on so a script to run each performance test's
63      perl script might be helpful.
64Note: The perl script is only used in one version of ICU. When you run regression tests,
65      it is recommended to run the tests from the later version of ICU.
66