I have been asked by the folks at work to recommend a Delphi profiler.

I have been asked by the folks at work to recommend a Delphi profiler.

I am utterly ignorant about Delphi profilers.

Can anyone recommend one that works with Seattle?

I'd be most grateful for any help.

Comments

  1. Just read about the new nexus one. Anxious to hear about it. AQtime gives good results but blue-screens regularly so you often need a few tries to get results.

    ReplyDelete
  2. We've been using AQTime since the early days with good results. Not tried the others yet.

    ReplyDelete
  3. Been using ProDelphi for years. Nice tool.

    ReplyDelete
  4. I've used Eric Grange​​​'s sampling profiler with success... http://delphitools.info

    ReplyDelete
  5. I remember a few years back AQTime bundled with Delphi was AVing in the IDE so often I had to uninstall it.

    ReplyDelete
  6. The AQTime IDE Plugin was junk. The standalone AQTime is quite good. Though for a quick glimpse I most often use SamplingProfiler.

    ReplyDelete
  7. From my experience the AQTime problems were with the IDE expert integration and not the standalone version.  NexusDB just updated their Quality Suite again by adding CodeWatch so it should be looked at as a strong competitor.  Note that if you plan on running AQTime on a virtual machine, you'll normally need a physical machine host to manage the licenses. (And you'll need to ensure to purchase the more expensive license... see https://support.smartbear.com/viewarticle/43532/)

    ReplyDelete
  8. Nick Hodges Hi Nick, as you will see, I just posted an update announcement of our Nexus Quality Suite, which contains several profilers, and other QA tools. You'll find the trial here:
    http://www.nexusdb.com/support/index.php?q=nqstrial

    ReplyDelete
  9. Sampling profiler, or just good old "press the pause button in the debugger and see what the call stack looks like"

    ReplyDelete
  10. We use AQTime (for profiling and deeper resource leak analysis). What I really like is the license server based floating license. Means the tool can be bought one in the company and used by all our developers.

    ReplyDelete
  11. Agreeing with those who say Sampling Profiler.  AQTime is an instrumenting profiler, which means it makes everything go ridiculously slow, and the instrumentation of your subroutines distorts the measurements.  (And the smaller and tighter the code, the more it gets distorted.)

    Sampling Profiler is a sampler, not an instrumeter, so you don't get that effect.  Plus it's free.

    ReplyDelete
  12. I'll probably add dbg-Spider to the list. Looks like vastly enhanced version of Sampling Profiler.

    ReplyDelete
  13. I have not found a sampling profiler that take into account the call stack trace. What if I see a heavy use of strings or midas library if I don't know from where exactly they are used?
    Line and procedure profiling in my source code is more valuable. Time and number of executions.
    For very small routines a sampling profiler can be better but it's not my case.
    And with Nexus the slowdown is almost imperceptible. Some years ago I used AQTime that comes with Delphi and app was very slow when profiling.

    ReplyDelete
  14. Aside. Has anyone any experience with VS built in profiling tools that have been added recently. They do look pretty swanky but I don't know how effective they are.

    ReplyDelete
  15. I had used Sampling Profiler for long time, but the lack of updates to support the recent Delphi versions, although it is simple to add the Library/Source Paths, makes me look for other solution, Spider - Delphi profiler did the job very well and, that is what I'm using, and as a plus the source code is available in github.

    ReplyDelete
  16. Thanks, Cesar Romero Good to know.

    ReplyDelete

Post a Comment