Jump to content

Blackfire profiler


Beluga
 Share

Recommended Posts

Ok, I've got everything set up on an Ubuntu 14.10 VM.. the agent, blackfire-php (Probe), a ProcessWire dev install, Chromium, Blackfire Companion extension.. But I ran into a problem.

When I try to profile my PW front page on localhost with the Chrome extension, it says:

Signature '..' is invalid

(I removed the actual signature)

I enabled logging:

https://blackfire.io/doc/configuration#probe-configuration

I also set up the server id & token in .htaccess like mentioned in the Apache Configuration Settings.

This is what's in /tmp/blackfire.log after my attempt at profiling:

Sat Jan 31 17:46:34 2015 (7606): [Debug] Found signature :
Sat Jan 31 17:46:34 2015 (7606): [Message] No key found in memory or key expired, continuing without validation
Sat Jan 31 17:46:34 2015 (7606): [Debug] Found network based probe stream (unix:///var/run/blackfire/agent.sock)
Sat Jan 31 17:46:34 2015 (7606): [Debug] Sending Blackfire-Query as of 'Blackfire-Query:
Sat Jan 31 17:46:34 2015 (7606): [Warning] Could not parse response
Sat Jan 31 17:46:34 2015 (7606): [Debug] Found Blackfire-Error, proxying as-is in HTTP header

(I removed signature & query).

Link to comment
Share on other sites

  • 1 month later...

Yeah, I gave up on trying to make it work. There is no support forum so I had no way of asking for help.

If any of you are feeling adventurous, there are apparently now a ton of ways to get it working in a more automated way or even pre-installed.

Chef: http://blog.blackfire.io/chef-support.html (still have to write a wrapper for webserver reloading)

Heroku: http://blog.blackfire.io/heroku-addon.html

Laravel Forge: http://blog.blackfire.io/blackfire-on-laravel-forge.html

Platform.sh: http://blog.blackfire.io/platformsh-webinar.html

Fortrabbit: http://www.fortrabbit.com/

For myself, PuPHPet would perhaps be the preferred route (don't want to pay for some platform just to test), so I subscribed to this issue: https://github.com/puphpet/puphpet/issues/1313

Link to comment
Share on other sites

  • 1 month later...
  • 6 months later...

I just installed the profiler on a local vagrant machine without problems. Yesterday after installing xdebug my site even timeouted for load intensive sites, which drove me nuts, but the profiler really does not intervene in load times at all. I've a profile from an edit page in the backend for anyone interested in how these profiles look like: https://blackfire.io/profiles/ed0fddee-769f-469d-9776-d1172445217e/graph

Edit: Might be gone in 24h as the free plan does store profiles only for a day.

  • Like 3
Link to comment
Share on other sites

  • 2 months later...

Sorry for raising this from the dead, but I've recently used it and it's absolutely marvelous. It will stay put on production servers unless you call it explicitly through the browser plugin, and it will profile anything you throw at it, PW, WP, frameworks, etc. Compared to xdebug, it's litterally miles ahead in my opinion.

This is a must have.

  • Like 1
Link to comment
Share on other sites

I can confirm this. I've set up a new dev box over the last few days and included blackfire from the beginning and it just works so nicely. I've yet to figure out if the "debugging features" do also allow for steping through the code, but even the performance analysis is so much worth.

  • Like 1
Link to comment
Share on other sites

Right, all the magic getters do have a (negligible imo) impact on performance but it's to be expected in a CMS.. there's always a cost to flexibility and convenience. Can't say I've really ever had performance problems with PW itself though.

I'd be interested to see a comparison between the same calls between PHP7 and 5.6 though.

Link to comment
Share on other sites

 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...