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 [-hVvaNAcCBXswiIRDPGOYZyQzxul] [-t sec] [-r results_dir] [-m
11 {0,1}] [-U path] [-g setup] [-J pid] [-T time] [-F file] [-W app] [-L
12 title] [-K comment] [-e app] [-E app] [-p percent] [-d percent] [-o
13 {0,1,2}] [-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 Developer workload
24 simulates code development in Linux environment
25 Reader workload
27 simulates text reading on laptop (mostly used to measure
28 battery life)
29 Playback workload
31 simulates laptop entertaining usage (produces constant
32 average load on the system)
33 3d game workload
35 simulates 3D-gaming on laptop (Unreal Tournament demo is
36 used to create this workload)
37 Office Activity workload
39 simulates laptop usage for different office activities
40 (based on OpenOffice.org office suit)
41 When started, test collects platform/OS initial info and if it's OK
43 prompts user to unplug AC adapter. After cable unplugged, workload
44 started. During the workload execution test harness collects various
45 system information (e.g. CPU load, battery drain, display state, CPU
46 frequency, etc...). After battery completely discharged user should
47 plug the AC cable back and boot the system. When it is done the
48 results are available.
49 There are several tools for result evaluation. They allow creating
51 report file for test run, to gather results into a table for system
52 comparison, and to draw graphs for different purposes.
53 Results - after the battery dies and the system booted back, the
55 results are available. They are stored in 'bltk/<wokload_name>.results'
56 directory (or in the directory, specified in -r option). If target
57 directory already exist the tool will add numeric extension to its name
58 (.001, .002 e.t.c.) The results consist of the following files (see
59 below for detailed description):
60 cmd In this file 'bltk' command with arguments are stored
62 infoi<N>.log (info1.log, info2.log, ...)
64 Here initial system info is stored. Another two files
65 (info1.log, info2.log) contains system info after AC adapter was
66 unplugged, and on 5% battery capacity remained. They are used to
67 check whether any changes occurred during test execution.
68 stat.log
70 Statistics generated by bltk harness are stored here. One
71 statistic line generated per 1 minute (or per number of seconds,
72 specified in -t option).
73 system<N>
75 When -k 1 is used, the system information is stored under this
76 directory. The numbers at the end of directory name have the
77 following meanings:
78 0 initial system info
80 1 system info after AC adapter was unplugged
82 2 system info on 5% battery capacity remained
84 version
86 this file contains version information
87 workload
89 the file contains info about workload
90 work_out.log
92 err.log
94 There are stored any error messages
95 warning.log
97 Contains warnings
98 work.log
100 Strings generated by USR1, USR2 signals from workload. String
101 format is the same as in the 'stat.log' file.
102 fail when test fails
104 score
106 Report
108 Report.table
110
112 -h, --help
113 Help; display a help message and then exits.
114 -V, --version
116 Version; display version number and then exits.
117 -v, --verbose
119 Verbose
120 -a, --ac-ignore
122 ignore ac adapter state check (on/off)
123 -N, --time-stat-ignore
125 disable time statistics
126 -A, --ac-stat-ignore
128 disable ac adapter statistics
129 -c, --cpu-stat-ignore
131 disable cpu load statistics
132 -C, --cpu-add-stat-ignore
134 disable cpu additional statistics
135 -B, --bat-stat-ignore
137 disable battery statistics
138 -X, --disp-stat-ignore
140 Disable display state statistics
141 -H, --hd-stat-ignore
143 disable hard drive state statistics
144 -t seconds, --report-time seconds
146 frequency of report line generation in seconds
147 -r results_dir, --results results_dir
149 name of results directory
150 -s, --stat-ignore
152 disable all statistics
153 -w, --work-stat-ignore
155 disable workload statistics
156 -m {0,1}, --stat-memory {0,1}
158 dump statistics directly on disk or keep in memory, if statis‐
159 tics are kept in memory, it will be dumped on disk at low
160 battery capacity, or at the test end
161 0 disk
163 1 memory (by default)
165 -i, --idle-test
167 idle test
168 -I, --idle
170 idle workload
171 -R, --reader
173 reader workload
174 -D, --developer
176 developer workload
177 -P,'--player"
179 playback workload
180 -G, --game
182 3D-gaming workload
183 -O, --office
185 office productivity workload
186 -U path, --user path
188 user-specified workload (path to executable)
189 -g routine, --user-init routine"
191 setup routines for user-specified workload
192 -Y, --discharging
194 battery discharge mode
195 -Z, --charging
197 battery charge mode
198 -J pid, --jobs pid
200 make jobs number
201 -T seconds, --time seconds
203 workload time
204 -F, --file
206 workload file
207 -W, --prog
209 workload program name of player (player workload, default
210 'mplayer') name of web-browser (reader workload, default
211 'firefox')
212 -L, --title
214 title of web-browser document
215 -M, --manufacturer
217 enable time and cpu load statistics only
218 -S, --show
220 demo/debug mode, one iteration only
221 -n, --show-num
223 demo/debug mode, 'show-num' iteration
224 -j, --show-cnt
226 demo/debug mode, 'show-cnt' sub iteration
227 -T seconds, --show-time seconds
229 demo/debug mode, debug time
230 -K comment, --comment comment
232 user comment for report
233 -e application, --init-prog application
235 run program before test starting
236 -E application, --init-prog-su application
238 run program as root before test starting
239 -y, --yes
241 auto 'yes' answer to all questions
242 -Q, --debug
244 debug workload (see cpu-load and disp-load below)
245 -p percent, --cpu-load percent
247 debug workload, the time cpu loaded in percent
248 -d percent, --disp-load percent
250 Debug workload, the time display on in percent
251 -o {0,1,2}, --output {0,1,2}
253 direct workload output:
254 0 file
256 1 file and console
258 2 /dev/null, other - console
260 -z, --debug-vars
262 debug option
263 -q file, --debug-vars-file file
265 debug option - debug variables file
266 -x, --dpms
268 debug option - try to use display power management
269 -u, --spy
271 debug option - try to find out unexpected system activity
272 -l, --simul-laptop
274 debug option, laptop simulation
275 -b percent, --bat-sync percent
277 debug option, battery critical capacity, default 5%
278 -f command, --user-field command
280 the output of user-specified command being added to statistics
281 Example: -f "cat /proc/acpi/thermal_zone/TZ01/temperature |
282 awk '{print }'"
283 -k num, --stat-system num
285 debug option, save system files, default 0
286
288 bltk -I or --idle
289 idle workload running
290 bltk -R or --reader
292 reader workload running
293 bltk -D or --developer
295 developer workload running
296 bltk -O or --office
298 office workload running
299 bltk -P or --player
301 player workload running
302 bltk -G or --game
304 game workload running
305 bltk -i or --idle-test -T 60 -t 1
307 idle test running for 60 seconds, stats interval 1 second
308
310 bltk.conf(5), bltk_report(1)
311
313 Konstantin Karasyov <konstantin.a.karasyov@intel.com>
314 Vladimir Lebedev <vladimir.p.lebedev@intel.com>
315BLTK 15 July 2008 BLTK(1)