-------------------------------------------------------------------------------------------------
Eloquent performance is typically the main reason for slow Laravel projects. A big part of that is a so-called "N+1 Query Problem". In this article, I will show a few different examples of what to watch out for, including the cases when the problem is "hidden" in unexpected places in the code.
What is the N+1 Query Problem
In short, it's when Laravel code runs too many database queries. It happens because Eloquent allows developers to write a readable syntax with models, without digging deeper into what "magic" is happening under the hood.
This is not only an Eloquent, or even Laravel, problem: it's well-known in the dev industry. Why is it called "N+1"? Because, in the Eloquent case, it queries ONE row from the database, and then performs one more query for EACH related record. So, N queries, plus the record itself, total N+1.
To solve it, we need to query the related records upfront, and Eloquent allows us to do that easily, with so-called eager loading. But before we get to the solutions, let's discuss the problems. I will show you 4 different cases.
Tối ưu query dự án laravel
Link : https://laravel-news.com/laravel-n1-q...
KẾT NỐI VỚI ĐỨC
Web: https://dayhoccongnghe.com/
Fanpage: / laptrinhchonguoimoibatdau
Group: / congdongdev
Fb: / ducnv
#lập_trình #ga_lap_trinh
Смотрите видео Eloquent Performance: 4 Examples of N+1 Query Problems - Tối ưu laravel, cải thiện tốc độ website онлайн без регистрации, длительностью часов минут секунд в хорошем качестве. Это видео добавил пользователь Meta Coder 01 Январь 1970, не забудьте поделиться им ссылкой с друзьями и знакомыми, на нашем сайте его посмотрели 1,53 раз и оно понравилось 3 людям.