On Sun, Mar 9, 2008 at 1:09 PM, YOUNSI RIADH <[EMAIL PROTECTED]> wrote: > As I heard that such commands may disturb the running system if they are run > periodically through crontab jobs
The process of running any cron job (even if it is "echo cron is still alive") likely has more overhead with it than having vmstat look at the various kstat values. If you have hundreds or thousands of disks, iostat may chew up a few cycles, but any system with such a large number of disks is likely to have enough CPU power that it is rather insignificant in the grand scheme of things. There is likely more to be gained in disabling per partition kstats (see sd(7D) and ssd(7D)) than there is in limiting use of vmstat or iostat. If you were asking about prstat or top, I would argue that they are both rather heavy commands and should be avoided except for when you need them. > Could you please tell me if there are equivalent commands in solaris 10 > using dtrace that can be used to identify performance problems cpu, memory > and disks Any dtrace command would either be duplicating effort that is done already when updating kstat data or would be simply reading the same kstat data read by vmstat and iostat. vmstat and iostat are already written and well tested. Use them. -- Mike Gerdts http://mgerdts.blogspot.com/ _______________________________________________ dtrace-discuss mailing list [email protected]
