Really nice challenge, a small tip, when eager loading you can also specify the columns you want from the relationship like this ->with('category:id,name'), it doesn't really matter here since in this case this is a very minor performance boost, but relationship could have like 20 columns, and this way you are loading only those you need for the query :)
Nice tip. This also reduces the data that is to be returned by DB, so less cpu intensive and also data transfer size is significantly low when transferring through Ajax.
I am not a PHP guy, I even don't like PHP. But I like to watch your videos, how you approach to the solutions, optimize things step by step. Thanks for your videos. Keep making ❤️
Thank you so much for this video, actually this was my first time using debugbar, and just following your tips I managed to reduce the queries in one of the pages from 800 queries to just 75 , and from 1400 models to 40 , also reduced memory from 26 mb to 15 mb. You are awesome. Thank you. Keep it up.
$object->relation = returns results for the relationship as result of sql query $object->relation() = returns query builder / eloquent instance on which one can perform other stuff. Respect from Pakistan
Thank you, wonderful explanation, you save my time once I googled how to minimize the number of query in model, but I didn't success, now I got idea how to optimize my queries.
First of all, allow me give my loud of applause for your great content on laravel and programming generally. Your videos have really shaped my laravel skills 👏. I do have a problem when it comes to memory(debugbar measurement) which even in a small page with just 3 queries (perfectly optimized) doesn't still go below 23mb and page load speed at/around 200ms. Thank you
@@LaravelDaily might be, because even the login page with no queries and just 2 views, still goes at 23mb. Thank you for the response. Is there a fix to this though?
This sure did work. On my local machine I'm running xampp server which seems to be the one with this problem. When i tested on a staging server running Lightspeed web server, everything seems to be stable. Thanks alot 😊
Hi sir, learn more alot from your videos. u use withCount and withAvg to a single relationship. Can you please make a video on aggregate relation methods like these and withSum for relationship's to relations like withSum('movies.category', 'column_name'). Thanks
Hi, I don't really see the goal of doing this, you just use the same functions and pass different relationships to them, and experiment. Not sure if my new video on a different scenario would add some significant content that is unclear.
Hi Povilas, I learned a lot from you, please confirm one thing, while adding a foreign key you did not drop the column, it isn't necessary to drop a foreign key column?
There are two different things: column and foreign key. So column existed but foreign key didn't. So there was nothing to delete, I just added foreign key to existing column.
Hello i am using laravel excel package and i have a little doubt, the excel file consist of students fee data, where they pay specific fee data. So suppose a student pay for tution fee, and hostel fee so there are two tables for that, one is parent table and another is child table. So suppose tution fee is 1000 and hostel is 500, the sum 1500 will be stored in parent table whose primary key will be stored in child table where fee details will be stored different rows, but it will be single row for parent table no matter how many payment student make it will only show the sum of amount
sir what about do not use refrence id but just do this $table->bigInterger('category_id)->unsigned()->index(); and in model define relation ??? does it slow ????
The index() itself will help you to get faster query, yes. But you do need a foreign key to avoid incorrect data, watch my video about it: th-cam.com/video/-77LnBSL2Zk/w-d-xo.html
@@LaravelDaily yeah I just watched a video where you explained this, about the differences of using query(). I'm watching all your videos, I just did a test and got the answer that I passed after being lay off my last job, I can safely say that, if everything go as planned as it seems like, you are one the biggest helpers here. Thank you so much for sharing your massive knowledge with the world!
I prefer to write my own SQL queries as opposed to eloquent I feel like when working with complex systems having allot of relationships defined in the model gets very complicated as opposed to just SQL. What are your thought's on this is not using eloquent in Laravel a bad thing as i almost never use it if I can help it?
"Eloquent models dispatch several events, allowing you to hook into the following moments in a model's lifecycle: retrieved, creating, created, updating, updated, saving, saved, deleting, deleted, restoring, restored, and replicating." (c) laravel.com
If our app have many visitors, we can optimizate this code with events hooks (on created new rating we can calculate Avg rating and save to Movie model, or create model like MovieStats - and run this code on diffrent threads), or move complex query to another server.
thanks povilas for this great tips 1-is there different between foreign and foreignId? because I always use foreignId I wonder which one is better to stick with it 2- take() and paginate() are some or different? because they both return specific amount of data in my challenge I used pagination
dude, with foreign you have to write unsignedbiginteger and foreign statement, but with foreignId, contains both lines , take seems like a LIMIT , paginate, is like a function that returns how many rows are, what page you are, etc sorry my english
1. Foreign() just created the foreign key, so you have to separately create the column itself. ForeignId() creates both column and foreign key. 2. Well, they serve different purpose, take() adds LIMIT 100 to the SQL query, and paginate() takes the parameters from GET request, then adds similar LIMIT to SQL and then provides Laravel with features like ->links() to show in the Blade.
Really nice challenge, a small tip, when eager loading you can also specify the columns you want from the relationship like this ->with('category:id,name'), it doesn't really matter here since in this case this is a very minor performance boost, but relationship could have like 20 columns, and this way you are loading only those you need for the query :)
Good tip bro
Nice tip.
This also reduces the data that is to be returned by DB, so less cpu intensive and also data transfer size is significantly low when transferring through Ajax.
I am not a PHP guy, I even don't like PHP. But I like to watch your videos, how you approach to the solutions, optimize things step by step.
Thanks for your videos. Keep making ❤️
Thank you so much for this video, actually this was my first time using debugbar, and just following your tips I managed to reduce the queries in one of the pages from 800 queries to just 75 , and from 1400 models to 40 , also reduced memory from 26 mb to 15 mb.
You are awesome. Thank you. Keep it up.
6:47 wow! that was soo cool and satisfying
this video is gold, thanks !
Excellent video!! Thanks for this. Your explanation is perfect and solve a lot of questions for me. Thanks!
$object->relation = returns results for the relationship as result of sql query
$object->relation() = returns query builder / eloquent instance on which one can perform other stuff.
Respect from Pakistan
Amazing !!!
This is best steps and very clear to refactoring query.
Waw! Need more cases
It's a wonderful sample that show what we do and what wee must do. Thanks
Thank you, wonderful explanation, you save my time once I googled how to minimize the number of query in model, but I didn't success, now I got idea how to optimize my queries.
Clean solution, good job
I love these challenges. Very satisfiying.
Good solution, we need more challenges.
This is gold
Thanks for the video. I have learnt a lot from your videos
Lol love the fact that it says 1.42 sec and the vid takes 4 seconds to open the page hahahaha but thank this helped me a lot
Best Video Ever
Thanks as always. Mine is PR 48. And now I'm here to learn how to really improve it :)
Perfect example, like frrom me, respect man!
Thank you so much really you are the best
First of all, allow me give my loud of applause for your great content on laravel and programming generally. Your videos have really shaped my laravel skills 👏. I do have a problem when it comes to memory(debugbar measurement) which even in a small page with just 3 queries (perfectly optimized) doesn't still go below 23mb and page load speed at/around 200ms. Thank you
That can be because of your webserver
@@LaravelDaily might be, because even the login page with no queries and just 2 views, still goes at 23mb. Thank you for the response. Is there a fix to this though?
Use a different web-server?
This sure did work. On my local machine I'm running xampp server which seems to be the one with this problem. When i tested on a staging server running Lightspeed web server, everything seems to be stable. Thanks alot 😊
very helpfull , thanks
Hi sir, learn more alot from your videos. u use withCount and withAvg to a single relationship. Can you please make a video on aggregate relation methods like these and withSum for relationship's to relations like withSum('movies.category', 'column_name'). Thanks
Hi, I don't really see the goal of doing this, you just use the same functions and pass different relationships to them, and experiment. Not sure if my new video on a different scenario would add some significant content that is unclear.
Espectacular. Muchas gracias :)
That's a satisfying refactor.
Very informative.❤
Very important video thank you
Thank you for your amazing video
Thanks. Very interestin. I also forgot to check indexes.... :(
That's some eloquent queries 😉
Great
Thank u nice challenge ❤️❤️
Greatness 🙏🙏
The best!
Awesome!
I didn't know there weren't foreign keys yet. I just assumed there would be. It was a mistake to do so hahaha
Hi Povilas, I learned a lot from you, please confirm one thing, while adding a foreign key you did not drop the column, it isn't necessary to drop a foreign key column?
There are two different things: column and foreign key.
So column existed but foreign key didn't.
So there was nothing to delete, I just added foreign key to existing column.
Hello i am using laravel excel package and i have a little doubt, the excel file consist of students fee data, where they pay specific fee data. So suppose a student pay for tution fee, and hostel fee so there are two tables for that, one is parent table and another is child table. So suppose tution fee is 1000 and hostel is 500, the sum 1500 will be stored in parent table whose primary key will be stored in child table where fee details will be stored different rows, but it will be single row for parent table no matter how many payment student make it will only show the sum of amount
Joss
Parfait, merci :)
sir what about do not use refrence id but just do this $table->bigInterger('category_id)->unsigned()->index(); and in model define relation ??? does it slow ????
The index() itself will help you to get faster query, yes. But you do need a foreign key to avoid incorrect data, watch my video about it: th-cam.com/video/-77LnBSL2Zk/w-d-xo.html
Первый! Спасибо!
Круто, что тут русскоговорящие есть
Any video is there on parsing huge xml data in Laravel
Hi sir. Can I add a foreign key to the pivot table? if yes, how to do it?
Thanks for advance
In my case same exactly same code requires 19MB of RAM always. Maybe it depends of the system.
Yes, I will talk about it in today's video.
Could you make it 1 query with a join on category? Is that good practise?
Yes also ok, but then you lose Eloquent magic like accessors, as it becomes a Query Builder.
@@LaravelDaily yeah I just watched a video where you explained this, about the differences of using query(). I'm watching all your videos, I just did a test and got the answer that I passed after being lay off my last job, I can safely say that, if everything go as planned as it seems like, you are one the biggest helpers here. Thank you so much for sharing your massive knowledge with the world!
Nice
I prefer to write my own SQL queries as opposed to eloquent I feel like when working with complex systems having allot of relationships defined in the model gets very complicated as opposed to just SQL. What are your thought's on this is not using eloquent in Laravel a bad thing as i almost never use it if I can help it?
"Eloquent models dispatch several events, allowing you to hook into the following moments in a model's lifecycle: retrieved, creating, created, updating, updated, saving, saved, deleting, deleted, restoring, restored, and replicating." (c) laravel.com
If our app have many visitors, we can optimizate this code with events hooks (on created new rating we can calculate Avg rating and save to Movie model, or create model like MovieStats - and run this code on diffrent threads), or move complex query to another server.
doesn’t ratings->count() automatically resolves to rating_count if the relation is eagerly loaded?
but then you eager load all the ratings, and you don't want to load them here, you specifically only want the count
What is the query and model monitor you are using in the video?
Laravel Debugbar
it's laravel debug bar
just type in Google barryvdh/laravel-debugb-bar
@@LaravelDaily Thankyou
@@abdulbasitsalah2918 Thankyou
thanks povilas for this great tips
1-is there different between foreign and foreignId? because I always use foreignId I wonder which one is better to stick with it
2- take() and paginate() are some or different? because they both return specific amount of data in my challenge I used pagination
dude, with foreign you have to write unsignedbiginteger and foreign statement, but with foreignId, contains both lines ,
take seems like a LIMIT , paginate, is like a function that returns how many rows are, what page you are, etc
sorry my english
1. Foreign() just created the foreign key, so you have to separately create the column itself. ForeignId() creates both column and foreign key.
2. Well, they serve different purpose, take() adds LIMIT 100 to the SQL query, and paginate() takes the parameters from GET request, then adds similar LIMIT to SQL and then provides Laravel with features like ->links() to show in the Blade.
@@LaravelDaily thank u
and one little note, after i apply your solution, i notice that you did not add foreign key for category in movie table
@@JuanMunoz-th3vn thank you, no your English is good
Yes good catch, it wouldn't speed up much in this case, but also a good practice.
What is the name of this Laravel debugger?
composer require barryvdh/laravel-debugbar
@@LaravelDaily thanks very much
Where can I get such a debugger?
composer require barryvdh/laravel-debugbar
@@LaravelDaily Thanks
What ide are you using?
Phpstorm
@@LaravelDaily and what theme pls?
Material Darker
@@LaravelDaily Thank you