We found 20 results for "performance".
Update May 2025: this course is outdated. The lessons of this course were updated and merged into a...
I've talked a lot about Eloquent on this channel but decided to pick the three most common mistakes related to performance.
A demo of a big e-shop simulation, where there are too many calculations are happening under the hood. Let's see why.
While optimizing Eloquent and DB performance in Laravel projects, it's not always about the number of queries or slowness of an individual query. There's one more important thing, let me show you, with an example.
Quick video, comparing two Laravel queries that perform almost the same task - querying by relationship. WhereHas() or join()?
Probably the most difficult step in the dev career is to jump from simple CRUD-like projects in the early years into some senior-level stuff with bigger architecture and a higher level of responsibility for the code quality. So, in this article, I tried to list the questions (and some answers) to think about, when working with large(r) Laravel projects.
The performance of our applications is one of the top things we should care about. Inefficient Eloquent or DB queries are probably no.1 reason for bad performance. In this tutorial, I will show you the top 3 mistakes developers make when it comes to Eloquent performance, and how to fix them.
One of the most common performance issues I've seen in Laravel is using Eloquent methods and relationships from Blade, creating unnecessary extra loops and queries. In this article, I will show different scenarios and how to handle them effectively.
In this video, I take the code written by one of the developers I mentor and show how to make the seeds run 3x faster.
In this video, step-by-step we will optimize a page loading from 30+ seconds to 0.2 seconds, by avoiding a foreach loop with Eloquent Attributes.
An experiment investigation I had in one demo project, with unexpected results.
This is a package to integrate PHP Debug Bar with Laravel.
The Laravel N+1 query detector helps you to increase your application's performance by reducing the number of queries it executes.
Real-time monitoring from the command line for Laravel applications.
My advice from practice, on the way of thinking and the approach how to test your application with a bigger amount of data.
How to identify the requests/endpoints that consume the most RAM in your application? Laravel Telescope may help you, with the information in its DB JSON fields.
In Laravel Eloquent, polymorphic structure is probably slower for queries. But by how much? Let's measure.
In Laravel and Eloquent, to avoid N+1 Query problems or to find slow SQL queries, you may use automatic tools. In this short tutorial, I will show you a few of them.
Database DB Auditor provide leverage to audit your MySQL database standards and also provide options to add constraints in table.
Optimize Your DB Queries with AI
