Magento 2 performance profiling and best practices

You cannot optimize
what you cannot measure

blackfire.io @blackfireio # blackfireio
How to measure PHP code
performance
● Microtime
● Benchmarking Libraries
● Application Performance Monitoring
● Load testing
● Profiling
https://blackfire.io/docs/24-days/03-what-is-blackfire

Measuring performance
impacts performance

Understanding the overhead
● Instrumentation
● Tools ready for production vs tools made for
development only
● Instrumenting all requests vs specific requests

Profiling is about measuring how much
resources your code is consuming
Wall time I/O CPU
Memory Network SQLHTTP Time
https://blackfire.io/docs/24-days/07-time-flavors

Time is volatile
● Time is not a stable metric. External factors such as machine load can
have significant impacts on wall time between two profiles of identical
code.
● Time is just a consequence of what happened in the code
● Use time to identify the slow parts in your code and then:
○ iterate and compare
○ write assertions on the root cause
● Profiling is about understanding how code works at runtime
https://blackfire.io/docs/24-days/12-tests-best-pratices

Callgraphs, timelines and more
● Find the function calls that
consume the most resources
● Know where to stop optimizing
● Trade-off time vs memory and
performance vs code complexity
● Profiling should not always be a
lonely activity

blackfire.io @blackfireio
#blackfireio
What are the issues
we encounter with
Magento 2

You cannot measure
what you don’t execute.

Varnish, can you ignore me?
acl profile {
# Allowed IP
"111.112.113.114";
}
sub vcl_recv {
if (req.http.X-Blackfire-Query && client.ip ~ profile) {
if (req.esi_level > 0) {
unset req.http.X-Blackfire-Query;
} else {
return (pass);
}
}
}

What about the Full Page Cache?
And all the others.

You have to compare.

The main issues
● SQL Queries
● Network
● CPU Time
● Memory
● I/O Wait
● External HTTP requests
● PHP & Bad PHP code

SQL Queries
● Use indexes and correct types.
● Limit the number of results you need.
● Avoid SQL requests…
● If you can’t avoid them, cache the output or
use LocalStorage/CacheStorage if insensitive information.
● Use Magento Repositories.
SQL Requests are the main issue.

● Use local networks with local IP addresses.
Network

CPU Time
● Avoid consuming operations: loops, events…
● KISS : Keep It Simple Stupid.

Memory
● Use the MagentoFrameworkModelResourceModelIterator for your
loops.
● Use PHP! Avoid creating so many objects when you can do the
operation with one function call.
● Use the Magento Dependency Injection.

I/O Wait
● Use php://memory and php://temp. Because Memory is always faster
than I/O.
● Optimize composer: composer dump-autoload --optimize --no-dev

External HTTP Requests
● Don’t do that.
● If you really have to: use RabbitMQ.
● And if you really have no choice: use asynchronous?
● And if you really really have no choice: use a small timeout and deal with
the errors properly.

PHP & Bad PHP code

PHP & Bad PHP code
● Upgrade to the latest version of PHP.
● Prefer a PHP core function to a lot of objects and methods.
●

The metrics
● Is Magento 2 installed? CE or EE?
● Is the cache enabled?
● Cache manipulation.
● Product loads.
● Interceptors measurement.
● Mode detector: production/developer/default.
● …

The metrics
magento2.all.cache.full_page.builtin.hit:
label: "Hit full page cache using builtin"
matching_calls:
php:
- callee: "=Magento[…]BuiltinPlugin::addDebugHeader"
caller: "=Magento[…]BuiltinPlugin::aroundDispatch"

The metrics
mymetrics.image.operation:
matching_calls:
php:
- callee: "/.*image.*/"
Will match imagecreate, getimagesize etc.

The recommendations
'The Magento 2 Full Page Cache should be enabled':
assertions:
- 'metrics.magento2.[…]full_page.builtin.hit.count == 1'
exclude:
- '.*/checkout.*'
- '.*/customer/section/load'
- '.*/catalogsearch'
[…]

The recommendations
'Do not make any image operation':
assertions:
- 'metrics.mymetrics.image.operation.count == 0'

Put some limits: .blackfire.yml
tests:
Pages should be fast enough:
path: /.*
assertions:
- main.wall_time < 850ms
- main.io < 500ms
- main.cpu_time < 500ms
Pages should not consume too much memory:
path: /.*
assertions:
- main.memory < 50M
- main.peak_memory < 75M
Homepage should not do too many SQL queries:
path: /
assertions:
- metrics.sql.queries.count <= 12
Checkout pages should be light:
path: /checkout/.*
assertions:
- metrics.output.network_out < 100KB

Scenarios
scenarios:
Home:
- /
Cart:
- /checkout/cart/
Login:
- /customer/account/login/

Profile Everywhere!

Magento 2 performance profiling and best practices

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Magento 2 performance profiling and best practices

Similar to Magento 2 performance profiling and best practices (20)

Recently uploaded

Recently uploaded (20)

Magento 2 performance profiling and best practices