1BLTK(1) Battery life tool kit BLTK(1)
2
6 bltk - tool kit is used to measure battery life and performance under
7 different workloads on Linux.
8
10 bltk [-hVvaNAcCBXswiIRPOYZyQzxul] [-t sec] [-r results_dir] [-m {0,1}]
11 [-U path] [-g setup] [-J pid] [-T time] [-F file] [-W app] [-L title]
12 [-K comment] [-e app] [-E app] [-p percent] [-d percent] [-o {0,1,2}]
13 [-q file] [-b percent] [-f command] [-k num]
14
16 The BLTK can be used with various workloads to simulate different types
17 of laptop usage. The following workloads are currently implemented:
18 Idle workload
20 collect statistics only (mostly used to measure battery
21 life)
22 Reader workload
24 simulates text reading on laptop (mostly used to measure
25 battery life)
26 Playback workload
28 simulates laptop entertaining usage (produces constant
29 average load on the system)
30 Office Activity workload
32 simulates laptop usage for different office activities
33 (based on OpenOffice.org office suit)
34 When started, test collects platform/OS initial info and if it's OK
36 prompts user to unplug AC adapter. After cable unplugged, workload
37 started. During the workload execution test harness collects various
38 system information (e.g. CPU load, battery drain, display state, CPU
39 frequency, etc...). After battery completely discharged user should
40 plug the AC cable back and boot the system. When it is done the
41 results are available.
42 There are several tools for result evaluation. They allow creating
44 report file for test run, to gather results into a table for system
45 comparison, and to draw graphs for different purposes.
46 Results - after the battery dies and the system booted back, the
48 results are available. They are stored in 'bltk/<wokload_name>.results'
49 directory (or in the directory, specified in -r option). If target
50 directory already exist the tool will add numeric extension to its name
51 (.001, .002 e.t.c.) The results consist of the following files (see
52 below for detailed description):
53 cmd In this file 'bltk' command with arguments are stored
55 infoi<N>.log (info1.log, info2.log, ...)
57 Here initial system info is stored. Another two files
58 (info1.log, info2.log) contains system info after AC adapter was
59 unplugged, and on 5% battery capacity remained. They are used to
60 check whether any changes occurred during test execution.
61 stat.log
63 Statistics generated by bltk harness are stored here. One
64 statistic line generated per 1 minute (or per number of seconds,
65 specified in -t option).
66 system<N>
68 When -k 1 is used, the system information is stored under this
69 directory. The numbers at the end of directory name have the
70 following meanings:
71 0 initial system info
73 1 system info after AC adapter was unplugged
75 2 system info on 5% battery capacity remained
77 version
79 this file contains version information
80 workload
82 the file contains info about workload
83 work_out.log
85 err.log
87 There are stored any error messages
88 warning.log
90 Contains warnings
91 work.log
93 Strings generated by USR1, USR2 signals from workload. String
94 format is the same as in the 'stat.log' file.
95 fail when test fails
97 score
99 Report
101 Report.table
103
105 -h, --help
106 Help; display a help message and then exits.
107 -V, --version
109 Version; display version number and then exits.
110 -v, --verbose
112 Verbose
113 -a, --ac-ignore
115 ignore ac adapter state check (on/off)
116 -N, --time-stat-ignore
118 disable time statistics
119 -A, --ac-stat-ignore
121 disable ac adapter statistics
122 -c, --cpu-stat-ignore
124 disable cpu load statistics
125 -C, --cpu-add-stat-ignore
127 disable cpu additional statistics
128 -B, --bat-stat-ignore
130 disable battery statistics
131 -X, --disp-stat-ignore
133 Disable display state statistics
134 -H, --hd-stat-ignore
136 disable hard drive state statistics
137 -t seconds, --report-time seconds
139 frequency of report line generation in seconds
140 -r results_dir, --results results_dir
142 name of results directory
143 -s, --stat-ignore
145 disable all statistics
146 -w, --work-stat-ignore
148 disable workload statistics
149 -m {0,1}, --stat-memory {0,1}
151 dump statistics directly on disk or keep in memory, if statis‐
152 tics are kept in memory, it will be dumped on disk at low
153 battery capacity, or at the test end
154 0 disk
156 1 memory (by default)
158 -i, --idle-test
160 idle test
161 -I, --idle
163 idle workload
164 -R, --reader
166 reader workload
167 -P, --player
169 playback workload
170 -O, --office
172 office productivity workload
173 -U path, --user path
175 user-specified workload (path to executable)
176 -g routine, --user-init routine"
178 setup routines for user-specified workload
179 -Y, --discharging
181 battery discharge mode
182 -Z, --charging
184 battery charge mode
185 -J pid, --jobs pid
187 make jobs number
188 -T seconds, --time seconds
190 workload time
191 -F, --file
193 workload file
194 -W, --prog
196 workload program name of player (player workload, default
197 'mplayer') name of web-browser (reader workload, default
198 'firefox')
199 -L, --title
201 title of web-browser document
202 -M, --manufacturer
204 enable time and cpu load statistics only
205 -S, --show
207 demo/debug mode, one iteration only
208 -n, --show-num
210 demo/debug mode, 'show-num' iteration
211 -j, --show-cnt
213 demo/debug mode, 'show-cnt' sub iteration
214 -T seconds, --show-time seconds
216 demo/debug mode, debug time
217 -K comment, --comment comment
219 user comment for report
220 -e application, --init-prog application
222 run program before test starting
223 -E application, --init-prog-su application
225 run program as root before test starting
226 -y, --yes
228 auto 'yes' answer to all questions
229 -Q, --debug
231 debug workload (see cpu-load and disp-load below)
232 -p percent, --cpu-load percent
234 debug workload, the time cpu loaded in percent
235 -d percent, --disp-load percent
237 Debug workload, the time display on in percent
238 -o {0,1,2}, --output {0,1,2}
240 direct workload output:
241 0 file
243 1 file and console
245 2 /dev/null, other - console
247 -z, --debug-vars
249 debug option
250 -q file, --debug-vars-file file
252 debug option - debug variables file
253 -x, --dpms
255 debug option - try to use display power management
256 -u, --spy
258 debug option - try to find out unexpected system activity
259 -l, --simul-laptop
261 debug option, laptop simulation
262 -b percent, --bat-sync percent
264 debug option, battery critical capacity, default 5%
265 -f command, --user-field command
267 the output of user-specified command being added to statistics
268 Example: -f "cat /proc/acpi/thermal_zone/TZ01/temperature |
269 awk '{print }'"
270 -k num, --stat-system num
272 debug option, save system files, default 0
273
275 bltk -I or --idle
276 idle workload running
277 bltk -R or --reader
279 reader workload running
280 bltk -O or --office
282 office workload running
283 bltk -P or --player
285 player workload running
286 bltk -i or --idle-test -T 60 -t 1
288 idle test running for 60 seconds, stats interval 1 second
289
291 bltk.conf(5), bltk_report(1)
292
294 Konstantin Karasyov <konstantin.a.karasyov@intel.com>
295 Vladimir Lebedev <vladimir.p.lebedev@intel.com>
296BLTK 15 July 2008 BLTK(1)