Red Gate forums :: View topic - Control when profiling begins
Return to RSS Feed Available

Search  | Usergroups |  Profile |  Messages |  Log in  Register 
Go to product documentation
ANTS Performance Profiler 6
ANTS Performance Profiler 6 forum

Control when profiling begins

Search in ANTS Performance Profiler 6 forum
Post new topic   Reply to topic
Jump to:  
Author Message

Joined: 14 Nov 2011
Posts: 2

PostPosted: Mon Nov 14, 2011 6:28 pm    Post subject: Control when profiling begins Reply with quote

I am currently using ANTS Performance Profiler V4.3.0.198.

There is no control in this version to select assemblies for profiling, or to launch the application and not begin profiling until a certain point. Since our application is large it can take up to 20 minutes when running within the profiler to get to the point where I'm interested in profiling.

The ability to attach to an already running process, or launch from the profiler with profiling disabled and then enable when ready _is highly desirable_. Has this feature been implemented in the latest version?
Back to top
View user's profile Send private message

Joined: 12 Oct 2011
Posts: 53
Location: Cambridge

PostPosted: Tue Nov 15, 2011 11:44 am    Post subject: Reply with quote


Attach to a .Net 4 process is a feature of the current version.

Back to top
View user's profile Send private message Send e-mail

Joined: 17 Aug 2006
Posts: 137

PostPosted: Wed Nov 16, 2011 1:05 pm    Post subject: Reply with quote

Another new feature of the later versions is a sampling profiler - in this mode the overhead of the profiler is low enough that it can be considered to be effectively nonexistent in most cases.

In the instrumentation modes, which capture the most detail, there's effectively no way to turn the profiler on or off: once the JIT has done its work, the instrumentation is in place and can't be changed. Additionally, the profiler would still need to track program state even when it was not measuring timings, which means the main effect of having an 'on/off' switch would be to make the profiler run slower (with the switch in either state). The best way to improve performance is to turn down the amount of instrumentation that is performed - in particular, line-level timings can require a lot of processor time to deal with.

Most profilers have an on/off switch in any case to make it possible to limit the final results to a specific time period. ANTS doesn't need this because it has the timeline and the ability to return profiler results for any time period by dragging out a region, so it's possible to just ignore the results from uninteresting times and easy to look at many different areas of the program in a single run.

This is particularly aimed at applications with long setup times: it means that it's not possible to make a mistake that would result in the interesting part of the data being lost, and also makes it easy to take a peek at the early data to ensure that the profiler is indeed capturing what's required.
Andrew Hunter
Software Developer
Red Gate Software Ltd.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic All times are GMT + 1 Hour
Page 1 of 1

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

Powered by phpBB © 2001, 2005 phpBB Group