continuous performance testing: why you should care

blackfire.io @blackfireio #blackfireio

Continuous Performance Testing> Why you should care


Christophe Dujarric @Chris_Dujarric Product guy. Loves simple things that solve real problems.

Paris, France

Blackfire.io/SensioLabs

christophedujarric.wordpress.com

/christophedujarric

Reason #1

Money!

-100ms +1%revenue -2.2s +15%

downloads -400ms+9%traffic


Application Perfomance……Monitoring?


Weather conditions

Third party services

Your Code

InfrastructuresFront-end


https://www.flickr.com/photos/guiseiz/6094701062

Wall Clock Time

Wall Time = CPU + I/O


function foo(){ bar();

echo 'foo';}

foo();

Inclusive Time


function foo(){ bar();

echo 'foo';}

foo();

Exclusive Time


I/O= Network + Disk

Business logic is key


gc_disable();

Improving Composer

up to 90% faster

Reason #2Continuous attention to technical excellence and good design enhances agility.

Agile Manifesto

From a Technology to a Product


Monitoring

Benchmarking

Load-testing

Profiling?


Measuring server response to simulated demand

Mainly Open Source tools

Load testing

Bees with Machine Guns


Assess the relative performance of servers

Benchmarking

SiegeHttpPerf

Apache Bench


Real traffic tracking | Crash reports | R.U.M.

Monitoring


Detailed insights on code performance

Open Source/legacy tools

Profiling

XHProf

abandon a website that takes more than 3 seconds to load

40% of users


Solving issues in production costs a lot more than solving them in development


Agile and Continuous Integration/Delivery thrive to test and automate testing but no tool could

do that for code performance

We want performance to become a major component of Continuous Integration/Delivery

and prevent issues before they occur in production.

thanks to tools which will continuously and automatically test and improve

application performance,

Reason #3

Because now you can.

Step 1: Set your objectives


Performance is business

T100ms 400ms


Pages should be fast

Pages should be light

Pages should not do too many SQL queries

Pages should not become slower

Write it like you think of it


# ~/workspace/project/.blackfire.yml tests: "Pages should be fast enough": path: "/.*" assertions: - "main.wall_time < 80ms" - "main.memory < 8M" - "main.peak_memory < 8M" - "main.io < 10ms" "Pages should not do too many SQL queries": path: "/.*" assertions: - "metrics.sql.queries.count <= 4" "Pages should be light": path: "/.*" assertions: - "metrics.output.network_out < 30KB" "Pages should not become slower": path: "/.*" assertions: - "percent(main.wall_time) < 10%" - "diff(metrics.sql.queries.count) < 2"

.blackfire.yml

Step 2: Circumscribe the issues


Profile visualization

Step 3: Fix and check


composer install --optimize-autoloader

Step 4: Make sure it won’t happen

(again)


TDD?


# ~/workspace/project/.blackfire.yml tests: "Pages should be fast enough": path: "/.*" assertions: - "main.wall_time < 80ms" - "main.memory < 8M" - "main.peak_memory < 8M" - "main.io < 10ms" - "metrics.composer.file_lookups.count == 0"

metrics: composer.file_lookups: label: Composer File Lookups layer: ~ matching_calls: php: - callee: =Composer\Autoload\ClassLoader::findFileWithExtension

Custom Metrics

Step 5: QA everywhere


Continuous Deployment

Several times a day


Completed 26 sprints

Marked 700+ stories and tasks as Done

rolled out 220 prod releases of the website

Merged 2,260 pull requests

In a year, we

Avg.

Christophe Dujarric - Product Manager [email protected]

@Chris_Dujarric

Fire up your PHP Apps Performance

continuous performance testing: why you should care

Software