I'm in the process of writing a daemon that uses libdtrace to collect performance data continuously. The only real problem I've run into is figuring out how to limit the amount of data I'm collecting.
I obviously don't need to know about every single IO or network event, just a sampling. The solution that I'm leaning towards is to have the daemon start and stop dtrace instrumenting at regular intervals. In order to avoid an appreciable performance impact from using dtrace for this type of work, does it make sense to start and stop dtrace all the time, or is it better to keep it running and throw away the data points I don't want? -- Peter Jones, http://pmade.com pmade inc. Louisville, CO US _______________________________________________ dtrace-discuss mailing list dtrace-discuss@opensolaris.org
