How can we help you today? How can we help you today?

Beta 4 Feedback

It's my first time using Ants Profiler (any version). I've used vtune in the past, mostly for C++.

I really like the UI in this product. The timeline really is a good idea. I felt like I could easily dig in to regions of interests, and perhaps even more important, separate out the regions of interests depending on user actions. With that said, I haven't spent enough time with the product to actually solve any performance issue, so I'll provide more feedback later. These are my initial thoughts, and they're very positive.

Here are some minor issues I ran into:

When I first run VS 2008 after installing the profiler, I could see ANTS 4 in the menu bar but the first 3 menu items were disabled, I didn’t know why. So I had to run ANTS 4 using Launch ANTS 4 Performance Profiler. I assume the other menu items would profile whatever exe is specified by VS 2008's "default startup project"?

I got an exception when changing some chart parameters - this never happens when running without the profiler:
System.ArgumentException: Parameter is not valid.
   at System.Drawing.Drawing2D.GraphicsPath.AddArc(Single x, Single y, Single width, Single height, Single startAngle, Single sweepAngle)
   at Dundas.Charting.WinControl.ChartGraphics.a(RectangleF , Color , Single , Color , Boolean , Int32 )
   at Dundas.Charting.WinControl.ChartGraphics.FillRectangleShadowAbs(RectangleF rect, Color shadowColor, Single shadowOffset, Color backColor)
   at Dundas.Charting.WinControl.ChartGraphics.a(PointF , MarkerStyle , Int32 , Color , Color , Int32 , String , Color , Int32 , Color , RectangleF , Boolean )
   at Dundas.Charting.WinControl.ChartGraphics.a(PointF , MarkerStyle , Int32 , Color , Color , Int32 , String , Color , Int32 , Color , RectangleF )
   at Dundas.Charting.WinControl.ChartTypes.PointChart.DrawPointMarker(ChartGraphics graph, Series series, DataPoint dataPoint, PointF point, MarkerStyle markerStyle, Int32 markerSize, Color markerColor, Color markerBorderColor, Int32 markerBorderSize, String markerImage, Color markerImageTranspColor, Int32 shadowSize, Color shadowColor, RectangleF imageScaleRect)
   at Dundas.Charting.WinControl.ChartTypes.PointChart.ProcessChartType(Boolean selection, ChartGraphics graph, CommonElements common, ChartArea area, Series seriesToDraw)
   at DC01.q.Paint(ChartGraphics graph, CommonElements common, ChartArea area, Series seriesToDraw)
   at Dundas.Charting.WinControl.ChartArea.b(ChartGraphics )
   at Dundas.Charting.WinControl.ChartPicture.Paint(Graphics graph, Boolean paintTopLevelElementOnly, RenderingType renderingType, XmlTextWriter svgTextWriter, Stream flashStream, String documentTitle, Boolean resizable, Boolean preserveAspectRatio)
   at Dundas.Charting.WinControl.ChartPicture.Paint(Graphics graph, Boolean paintTopLevelElementOnly)
   at Dundas.Charting.WinControl.Chart.OnPaint(PaintEventArgs e)
   at System.Windows.Forms.Control.PaintWithErrorHandling(PaintEventArgs e, Int16 layer, Boolean disposeEventArgs)
   at System.Windows.Forms.Control.WmPaint(Message& m)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

TreeView is my favourite so I was happy it was the default

Didn’t know what the red asterisks were beside some function name – tooltip to explain would be useful. Oh, I guess there is a tooltip to explain it – but the tooltip says other things as well, might be useful to include the red * in the tooltip beside the description that applies to it (and possibly a clickable area that explains how methods selected for optimization are selected?)
jtalbot
0

Comments

2 comments

Sort by
  • James Moore
    Thanks for the feedback!
    When I first run VS 2008 after installing the profiler, I could see ANTS 4 in the menu bar but the first 3 menu items were disabled, I didn’t know why. So I had to run ANTS 4 using Launch ANTS 4 Performance Profiler. I assume the other menu items would profile whatever exe is specified by VS 2008's "default startup project"?

    You are right, can you confirm you didn't have a project loaded at this point? If you did what type of project was it and how many projects were there in your solution?
    I got an exception when changing some chart parameters - this never happens when running without the profiler:
    I have had similar things happen to me when profiling, this can often be due to the profiler's overhead slowing something down a bit which then exposes some sort of race condition. This looks like it is totally internal to Dundas which might make finding the exact cause difficult. Which version of the Dundas charts component are you using?

    Once again thanks for taking the time to provide us with feedback, it is very much appreciated.

    James
    James Moore
    0
  • jtalbot
    James Moore wrote:
    Thanks for the feedback!
    When I first run VS 2008 after installing the profiler, I could see ANTS 4 in the menu bar but the first 3 menu items were disabled, I didn’t know why. So I had to run ANTS 4 using Launch ANTS 4 Performance Profiler. I assume the other menu items would profile whatever exe is specified by VS 2008's "default startup project"?

    You are right, can you confirm you didn't have a project loaded at this point? If you did what type of project was it and how many projects were there in your solution?

    There's a solution loaded, and the solution has 62 projects. 6 of those are executables, the rest are class libraries. All in C#. I've changed the start-up projects to different exe's or class libs, and the menu items are always disabled. I tried switching to simpler solution with one project and in that one the menu items are enabled. Switching back to the big solution, the menu items are disabled again.
    James Moore wrote:
    I got an exception when changing some chart parameters - this never happens when running without the profiler:
    I have had similar things happen to me when profiling, this can often be due to the profiler's overhead slowing something down a bit which then exposes some sort of race condition. This looks like it is totally internal to Dundas which might make finding the exact cause difficult. Which version of the Dundas charts component are you using?

    Version 5.5
    jtalbot
    0

Add comment

Please sign in to leave a comment.