![]() ![]() Restart Apache and you are all set, the site should be communicating with the correct environment. Add the following lines inside the directive, adding the correct credentials: Login to the dev server and find the vhost file, i.e. It is fine to have http authentication.Ĭlick on the newly created env and take note of the generated Server ID and server token credentials: Note that the url must be accessible from the outside (DNS must be set). ![]() * Is it a development environment? Leave unchecked Setting up an environmentįor each site you want to monitor, you need to create a new Environment in Blackfire: If this is not the case, is a good place to start. It assumes that you already can run adhoc profiles. This article will present a step by step process to accomplish this. Our use case concerned the dev servers - we wanted to check nightly that the newly introduced code does not break performance. Thresholds can be defined and the team can get alerts if certain limits are hit. This should be tested automatically part of the build process, so Blackfire comes to the rescue with a way to run profiles that check for key performance metrics, like used RAM, processor, SQL queries etc. ![]() In a nutshell, performance should be part of testing, each deployment should make sure that the application still performs decently. The concept of "performance as a feature" caught our attention. Recently we decided to dig deeper into the extra features. We have been using it for a while to do adhoc performance fixes. It's easy to install, safe to have it in production and secure. Blackfire.io is one of the best profiling tools out there. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |