Systems | Development | Analytics | API | Testing

Every so often, a careful profiling analysis of your application detects the bottleneck in third-party code and there is little remedy for you to override or change that code. In this blog post I want to present a solution to fixing performance problems in third-party libraries by using the composer patches plugin. I use the the Symfony ErrorHandler as an example.

We strive to improve clarity and user-friendliness, and have thus focused our efforts on several features that align with this objective. Our new Sidebar Menu, the Release Tracking Feature and an increased comparison range for Releases and Markers as well as the possibility to show error messages in notifications all fall into this category. Summary.

Tideways is joining the Open Source Pledge because we want to make a public commitment on our various open source contributions. Not only do we rely on open source software in our product Tideways, we are also building our business on top of the open source language PHP and its continued success. The mission of the recently started Open Source Pledge initiative is to establish a new social norm in the tech industry of companies paying Open Source maintainers.

The upcoming PHP 8.4 release will include the brand-new feature “property hooks”, a mechanism to add logic to a class property when read from or written to. One benefit of this feature is that you do not need to protect property access with a private property and public getter/setter methods anymore. You can find out how this feature works in the RFC and other places, but in the spirit of this blog we want to focus solely on the performance implications.

Sometimes, performance is the primary requirement when you are picking a third-party library to solve a task in your application. For CPU intensive work, there are often similar alternatives that you can choose from: To find out which one of them is more performant for your use-case, you can set up an experiment with microtime/hr_time calls and run them against each other. But: this provides fewer insights than running your tests directly with a Profiler such as XHProf or Tideways!

When using MySQL and InnoDB you will inevitably run into lock timeouts sometime, somewhere. We have recently started seeing this with some of our Shopware 6 customers in their storefronts or worker queues, so I was reminded to go back to 2017 in our codebase when we put a fix in place. In our case, this happened on tables that were constantly written to from many different sources in the code base.

Get the cake, Tideways is turning ten! Exactly on this day ten years ago, we lifted the veil on Tideways’ predecessor and thus began our exciting journey that continues to this day. We would like to celebrate by presenting interesting new features to you. Summary: Don’t miss out on our webinar that will guide you through these new features, taking place July 3rd starting at 3 pm.

PHPs compiler and bytecode cache OPcache not only cache the compile step from PHP source code to virtual machine bytecode, they also include optimizations that can produce faster bytecode: For example PHP can: For PHP 8.4 Tideways sponsored the work of our colleague Tim to add another compiler optimization for the function sprintf().

A few weeks ago, Andrey from Ecommlab contacted me to ask me about a strategy to get performance insights from Tideways into Shopware 6 checkout. The store of our joint customer “Bär Schuhe” was slow for customers during the order confirmation process.

This is the story of the manufacturing of seven-league boots for a function that is responsible for processing XML/HTML data in the PHP library. Optimizations in the PHP standard library, like here in ext/dom, have the potential to speed up the performance of applications significantly by an upgrade to the current PHP version.