6 Comments

  1. Nechama
    December 1, 2016 @ 7:02 am

    Why do you say that “P3 Profiler is next to useless”??

    Reply

    • David H.
      December 9, 2016 @ 1:12 pm

      The P3 profiler is next to useless for a LOT of reasons. The number 1 reason is that it itself consumes a lot of resources. The number 2 reason is it’s innacurate – it didn’t report that Datafeedr was causing my site slowdown for example (because my API license had expired as it turned out, causing 2x 30s HHTP Request timeouts). The number 3 reason is that when it DOES successfully identify the correct plugin that is causing performance problems, it doesn’t identify the source of the problem – e.g. database table scan, to much data retrieved, php loops, function name or anything. It’s crap.

      Reply

      • Max
        December 10, 2016 @ 4:48 am

        …also, P3 doesn’t support PHP 7 =(

        Reply

        • David H.
          December 12, 2016 @ 3:50 pm

          Well there you go then – to be honest, I’m not surprised. It was made by the guys over at GoDaddy and while they’re good at domain names, they’re not so good at plugin development.

          Reply

  2. Joel Milne
    December 31, 2017 @ 6:28 am

    I tried Xdebug profiler with WinCacheGrind but none of the cachegrind files would load properly. They might be too big? They average 8-12mb and I saw a page that suggested 8mb is about the limit. Any suggestions of a workaround or other viewer to use (on Windows)?

    Reply

Leave a Reply to Joel Milne Cancel reply

Your email address will not be published. Required fields are marked *