On 03/21/2014 06:58 AM, Bob Friesenhahn wrote: > On Mon, 17 Mar 2014, Michael Schuster wrote: > >> One more idea that comes to mind: use dtrace to find out which part of >> the code's being "exercised" while >> you're testing - use something tick-based (I'm fairly sure you'll be >> able to find something better than I'd be >> able to cook up, so I won't ;-). Then at least you have an idea >> whether your theory is a good one. > > Is DTrace actually useful for a program which runs for less than one > second? DTrace typically collects data at 999Hz. There could be a > shortage of samples.
If your program runs for less than a second it's hard to get meaningful data with any tool unless you do things such as turn off interrupts, create processor sets, pbind, etc. as the effects of traditional multi-user noise can be quite high. Robert ------------------------------------------- illumos-discuss Archives: https://www.listbox.com/member/archive/182180/=now RSS Feed: https://www.listbox.com/member/archive/rss/182180/21175430-2e6923be Modify Your Subscription: https://www.listbox.com/member/?member_id=21175430&id_secret=21175430-6a77cda4 Powered by Listbox: http://www.listbox.com
