Drastically Improve Query Time From 4 seconds to 70 milliseconds (50 - 60 times faster)

[@Laratips]

Get $15 credit by using code "LARATIPS" which can last almost a month. Cloudways Web Hosting: platform.cloudways.com/signup?id=1029148&data1=bw&coupon=LARATIPS Cloudways offers peace of mind and flexibility so you can focus on growing your business and reaching new milestones instead of dealing with server management. With Cloudways, you get an optimized stack, managed servers, backups, staging environment, integrated Git, pre-configured, Composer, 24/7 support, and the choice of five cloud providers: AWS, DigitalOcean, Linode, Google Cloud, and Vultr

[@Laratips]

Hey Guys, just wanted to share that don't go and create many indexes in your application. There is one downside of it as well. Yes, it increases the read performance of your application but it will decrease the write performance. It means when you store something in the table with lots of indexes, it will take a lot of time to actually store the data in the table. So, if your application does more reads than writes, you can add more indexes but the lesser the indexes better it is. Also, always check the performance of your application and roll back if necessary after adding an index.

[@BraderGeoYT]

I'm applying as a Laravel Developer for my next job and this really helped me alot to prepare and this is very useful thanks for the tip!

[@VitorJustin]

Great tip! Tks for sharing!

[@uchchhash-dev]

Great video! Thanks for the effort. Do you still plan to make videos regularly? Your last video was a few months ago

[@vmmismagic]

amazing explanation!

[@musicfactoryPH]

Very big help. Thank you so much

[@Laratips]

You're welcome!

great leson

[@Laratips]

Thanks

[@OnlinePseudonym]

Really insightful - thanks very much 🙂

[@Laratips]

Glad it was helpful!

[@imranlashari6578]

@laratips what about if i am using vue js as frontend and laravel as backend, i need to check every API call query execution time to optimize it

[@alnahian2003]

Cool! Learned something new and helpful.

[@Laratips]

Glad it was helpful!

[@farhanisrak8688]

Can you please tell which extension you're using for checking those queries?

[@fatchurrosi4386]

using laravel debug bar

[@farhanisrak8688]

Thanks @@fatchurrosi4386

[@bhavyakumarpanchotiya8254]

What is use of Carbon ...make the video on that..

[@Laratips]

It is basically a wrapper around PHP's DateTime class but much more readable api. Sure I will make one. Thanks for the video idea. :)

[@bhavyakumarpanchotiya8254]

@@Laratips Thank you sir

[@ramonm8039]

What is the name of the tool to see Queries??

[@julienSibille]

Laravel debugbar

[@ramonm8039]

@@julienSibille Thanks!

[@johnp6115]

Thanks for the tip, awesome!

[@lchig0]

Great vid buddy

[@Laratips]

Thanks

[@nathanstanfordsr]

awesome tip thanks

[@mirshodmustafoyev2524]

What happens if we use second query for non indexed data ? Gets less time than 4s or not ?

[@hizkielputra1195]

thank you

[@shahriyarhosseinzadeh4409]

Hey , please turn on subtitle

[@fahathamm3965]

Can i use collection for cout... if i use collect how much kuch sec take it.. which one is better..? Thank you recent addict laravel channel one of the subscriber

[@Laratips]

Always use eloquent or database layer instead of collection if possible. The time taken depends on how many data u have in collection. You can check the time by logging the time before and after the collection execution. Thanks for subscribing. ♥️

[@Vikaskumar-ur5di]

which package are used in laravel debug

[@Laratips]

Laravel debugbar

[@taskinurrahman6650]

Use count(id) instead of count(*)

[@impostor8984]

no

[@Xaero324]

This has been debunked. That may have been true very long ago, however, DBMS are now optimized and would prefer you use count(*). In short: count(*) !== select(*)

[@LukePighetti]

What tool are you using to show the Laravel query performance?

[@Laratips]

It's a laravel package called Laravel Debugbar

[@diomandesouleymane6621]

Great tip

[@BijayaNamna]

Are you from Nepal ? You accent seems like that

[@Laratips]

Yes

[@MudassarYaseen]

Great

[@tusharnain6652]

But it's gonna cost WRITE Operations.

[@jlbciriaco3142]

just think about what the user will do more: it will update the data or just see the data? generally is more acceptable a slow write operation than a slow read operation.

[@kapadiajanak]

Laravel socket io lesson

[@sri3235]

Thank you

[@MikdanJey]

Great

[@Warkim]

Thank you