1bench_intro(n) Benchmarking/Performance tools bench_intro(n)
2______________________________________________________________________________
6
8 bench_intro - bench introduction
9
11 The bench (short for benchmark tools), is a set of related, yet differ‐
12 ent, entities which are working together for the easy creation and exe‐
13 cution of performance test suites, also known as benchmarks. These are
14 [1] A tcl based language for the declaration of test cases. A test
16 case is represented by a tcl command declaring the various parts
17 needed to execute it, like setup, cleanup, the commands to test,
18 etc.
19 [2] A package providing the ability to execute test cases written in
21 that language.
22 Which of the more detailed documents are relevant to the reader of this
24 introduction depends on their role in the benchmarking process.
25 [1] A writer of benchmarks has to understand the bench language
27 itself. A beginner to bench should read the more informally
28 written bench language introduction first. Having digested this
29 the formal bench language specification should become under‐
30 standable. A writer experienced with bench may only need this
31 last document from time to time, to refresh her memory.
32 [2] A user of benchmark suites written in the bench language has to
34 know which tools are available for use. At the bottom level
35 sits the package bench, providing the basic facilities to read
36 and execute files containing benchmarks written in the bench
37 language, and to manipulate benchmark results.
38
40 This module and package have been derived from Jeff Hobbs' tclbench
41 application for the benchmarking of the Tcl core and its ancestor "run‐
42 bench.tcl".
43
45 This document, and the package it describes, will undoubtedly contain
46 bugs and other problems. Please report such in the category bench of
47 the Tcllib Trackers [http://core.tcl.tk/tcllib/reportlist]. Please
48 also report any ideas for enhancements you may have for either package
49 and/or documentation.
50 When proposing code changes, please provide unified diffs, i.e the out‐
52 put of diff -u.
53 Note further that attachments are strongly preferred over inlined
55 patches. Attachments can be made by going to the Edit form of the
56 ticket immediately after its creation, and then using the left-most
57 button in the secondary navigation bar.
58
60 bench, bench_lang_faq, bench_lang_intro, bench_lang_spec
61
63 bench language, benchmark, performance, testing
64
66 Benchmark tools
67
69 Copyright (c) 2007 Andreas Kupries <andreas_kupries@users.sourceforge.net>
70tcllib 1.0 bench_intro(n)