Blog
We at Tideways are working on PHP performance 24/7 and share this knowledge with the community.
Understanding complex request traces is one of the hardest parts of performance analysis. In this Release, we focused on making this significantly easier in Tideways. The Timeline has been redesigned to provide a clearer view of how requests are executed, with new layout modes, improved navigation, and a more consistent span model. These changes help […]
10 years ago, Benjamin founded Tideways with a clear goal: support PHP developers and help build faster, more reliable websites. Since then, more than 2,000 customers have used Tideways to gain better visibility into their PHP applications. Seeing that web applications are slow without understanding why sparked an idea for Benjamin, that ultimately led to […]
If you are using release events in Tideways to mark deployments of your application, then you will happy to hear that we have finally created notifications for them. Starting with Slack, Hipchat and Flowdock, you can now get a notification in two cases:
Your web applications usually runs in multiple contexts: the webserver, inside workers and as a cronjobs and it might even include calls to other micro- or SoA-services.
We are expanding our support for notifications about your applications performance with a Weekly Report notification that can be sent every Monday morning to Slack, Mattermost, Flowdock or HipChat.
After a slow December of vacation and holidays we are slowly picking up steam again and are releasing the first new features of 2017 with an improved history and server metrics for traces.
Timeouts are a rarely discussed topic and neglected in many applications, even though they can have a huge effect on your site during times of high load and when dependent services are slow. For microservice architectures timeouts are important to avoid cascading failures when a service is down.
If you are using Magento, Shopware, Oxid, a CMS or any other off the shelf software, then usually they ship both the frontend and the backend in a single application. For self-developed applications with Symfony or other frameworks this is often the case as well.
Along with the continous increase in computing power, the relative difficulty of breaking hashing algorithms decreases. It might occur that during the lifetime of a project, one algorithm becomes obsolete, or due to various reasons, the necessity of migrating to another algorithm becomes inevitable.
If you are using Sessions in PHP (the odds are very high) then you should know that write and read access to them is using pessimistic locking which means no two requests can run in parallel with the same session open.
When the performance of your application changes you want to know the reasons why. In the last month we have kept relasing feature after feature that makes this easy and quick and Snapshots was one of them.