Sub-processes cost time in shell scripts - try using a
case instead of the multiple
if [...] statements -
case is a built-in and is thus far faster than the sub-processes necessary to execute
if [...].
Maybe something (untested) along the lines of...
>$1.out
unset stat int cpu scpu
echo "Starting rebuild of $1 into $1.out"
while read line ; do
case $line in
END)
cpu=`expr $cpu / 60`
# Write data line
echo "$int,$cpu" >>$1.out
unset stat int cpu scpu
rec=`expr $rec + 1`
echo "`date`:Wrote record: $rec"
;;
*GMT | \
*SAST)
int=`echo $line|cut -c12-16`
;;
vmstat\ 2\ 60:)
stat=1
;;
procs |\
avm)
:
;;
*)
scpu=`echo $line | awk '{ print $16 "+" $17 }'|bc`
cpu=`expr $cpu + $scpu`
;;
esac
done < $1
echo "Complete!"
HTH ,
A user level that continues to overstate my experience :-))
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.