Re: Shark time limit
Re: Shark time limit
- Subject: Re: Shark time limit
- From: Rick Altherr <email@hidden>
- Date: Wed, 1 Aug 2007 09:05:51 -0700
On Jul 31, 2007, at 1:55 PM, kwiley wrote:
Okay, I *finally* figured out why Shark runs "run faster" than
nonshark runs. They don't actually run faster, they just flake out
after thirty seconds without telling you. If I enable the mini
config editor it clearly shows a time limit for cutting off the
shark run at thirty seconds. I wish that had been easier to find.
Now, I haven't found a very easy method to modify that. Say I want
to run for sixty seconds instead. When I launch Shark from XCode I
do not get an opportunity to modify that setting before the run
begins. I have to cancel the run, kill the process in Activity
Monitor, modify the time limit, and then reinitiate the run. UGH.
You could do the launching from within Shark rather than using the
menu item in Xcode. If you leave Shark running, you can modify the
settings in the mini-config editor, then use the launch option (Set
the target to Process, then in the process list, the first option is
Launch). You can use the launch option as often as you want from there.
We are aware that there is no way currently to select which
configuration or what settings you want to use when using the launch
from Xcode method. This will be changed in a future release.
Can I modify the default time limit somewhere? I don't see a
preference for this anywhere.
You could create a new configuration by duplicating the one you are
trying to use. Then, you can modify the time limit on the new
config. By selecting the new config in the config popup and then
quiting Shark, it will remember that that was the last used config
and thus it will be used with you use the launch from Xcode.
To do this, open the configuration editor (Config->Edit), then select
the config you wish to use. Click the Duplicate button. Now, modify
the settings for the config and click OK. Select the config you just
created and then quit Shark.
It's generally annoying that I have manually kill the process being
tested with Activity Monitor. Can't shark kill the process for me
at the same time that it times out and stops sampling the process?
We've had requests both ways actually. Some people want the launched
process to continue, some want it to be killed. If you have a strong
feeling on this, please file a bug report.
Thanks.
Thank you.
______________________________________________________________________
__
Keith Wiley email@hidden http://www.cs.unm.edu/
~kwiley
"Yet mark his perfect self-contentment, and hence learn his lesson,
that
to be self-contented is to be vile and ignorant, and that to aspire is
better than to be blindly and impotently happy."
-- Edwin A. Abbott,
Flatland
______________________________________________________________________
__
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40apple.com
This email sent to email@hidden
--
Rick Altherr
Architecture and Performance Group
email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden