On Mon, Jul 11, 2011 at 10:20 AM, Scott Shurr <scott.sh...@oracle.com> wrote: > > My customer still thinks this is a bug: > > ********** > We think that DTrace is not working as designed. Therefore we wanted to > report a bug for DTrace. Thank you for the answers from mailing list, but > these do not solve our problem. > > The DTrace script that we describe in the document results in "dynamic > variable drops", if the system is heavily loaded for a longer period of time > (around 24 hours). We assume that this is not the intended behavior of DTrace.
This assumption is wrong. It is a principal tenet of DTrace's design that it will not critically interfere with production services. This means, for example, that DTrace being starved for resources will not result in a system hanging until resources are freed. This is also the reason for DTrace's lack of looping facilities in its D language (and byte compiled instruction set). Nico -- _______________________________________________ dtrace-discuss mailing list dtrace-discuss@opensolaris.org
