Skip to content

15 Comments

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

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

    Reply

    • Anon
      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

        • Anon
          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

  3. Sunny
    August 31, 2018 @ 7:54 pm

    Any options for shared hosting?

    Reply

  4. Peter B.
    February 21, 2019 @ 11:26 am

    I’m trying to get this installed, but I’m not getting past these two ->
    Run: ./configure
    Run: make

    It says throws an error at the first command:
    Check for supported PHP versions… configure: error: not supported. Need a PHP version >= 7.0.0 and < 7.3.0 (found 5.4.16)

    I've disabled 5.4.16 in Plesk but that doesn't seems to work

    Reply

    • Dave H.
      February 21, 2019 @ 11:57 am

      You should ensure you generate the script from your OWN phpinfo.txt file. Instructions included above for how to generate that. Don’t follow my steps, as they’re particular to that specific server.

      Once you generate your phpinfo file, copy/paste the contents to the link above where it will then provide specific instructions for your server.

      Reply

  5. Peter B.
    February 21, 2019 @ 3:12 pm

    Hi Dave,

    Thx for your speedy reply 🙂 It worked….
    Any suggestions hwo to fix 98.25 php::unserialize? 🙂

    Reply

    • Dave H.
      July 16, 2019 @ 10:49 am

      Is this 98% time used by unserialize?

      That probably reflects using an object cache?

      Reply

  6. Stefan
    June 14, 2019 @ 3:09 pm

    Wheres the onsite chat for contacting you? no form? nothing…

    I want a performance analyse…You can contact me for more details, see my mail…

    Reply

    • Dave H.
      June 18, 2019 @ 7:44 pm

      Hi – we temporarily removed the onsite chat. You can email me at [email protected].

      Reply

      • Krzysztof T.
        June 21, 2019 @ 3:28 pm

        Please check your e-mail or facebook (regarding FWW existing filter widget attribute urls bug).

        Reply

Leave a Reply

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

CYBERFUNDAY 40% discount coupon extended to Friday 9th December + join our Discord community and read the rules for an extra 20% discount coupon.