Sun 97-12-07 Stan Ryckman <stanr(_at_)sunspot(_dot_)tiac(_dot_)net>
list.procmail
|
| Comparing byte sizes on disk means nothing here... these things
| may or may not have been stripped. Any symbol tables included
| in the byte counts you see above won't affect process start-up time.
|
| The "size" command will give a better handle on what will be
| needed in starting a process. The three segments may each have
| their own overhead, though, and the relative contributions of those
| segments to startup time may well be system-dependent.
Hi Stan, thank thank you for correction. How would you interpret this
instead:
awk: 72727 + 51316 + 15317 = 139360
sort: 173225 + 18496 + 183076 = 374797
sed: 237248 + 16992 + 56252 = 310492
grep: 221591 + 16176 + 53816 = 291583
perl4: 502220 + 36044 + 65632 = 603896
perl5: 633812 + 69612 + 2385 = 705809
gawk: 160018 + 5264 + 7168 = 172450
size produces section size information for each section in the object
files. The size of the text, data and bss (uninitialized data)
sections are printed along with the total size of the object file. If
an archive file is input to the size command, the information for all
archive members is displayed.
What should we look for if we were to compare performances?
jari