Read on Twitter
I'm happy to this performance achievement in Laravel Vapor after few tweaks. I think I can improve even more, but I'll sort out this later.
Reading the tweets by @JackEllis , and the Queues book by @themsaid and @reinink Eloquent performance really helped +
Thread:
Reading the tweets by @JackEllis , and the Queues book by @themsaid and @reinink Eloquent performance really helped +
Thread:
I personally get motivated by Fathom. It just run smoothly. And more motivated by this tweet:
https://twitter.com/JackEllis/status/1294331221162385408
But I waited very anxious for the Laracon Talk. The talk was amazing, with a lot of useful information. Jack was also very kind answering my e-mails. +
https://twitter.com/JackEllis/status/1294331221162385408
But I waited very anxious for the Laracon Talk. The talk was amazing, with a lot of useful information. Jack was also very kind answering my e-mails. +
I didn't buy his course (I should) but I'll advertise because I face a database downtime for a running Job, and he mentions that. 
https://serverlesslaravelcourse.com/
https://serverlesslaravelcourse.com/
@themsaid Mohamed book (that you SHOULD buy if you want to become a King of Queues) it contains a lot of tips, samples about Queues and a section for applications running on Vapor. Also his blog posts.
https://learn-laravel-queues.com/
https://divinglaravel.com/cost-performance-optimization-in-laravel-vapor
https://learn-laravel-queues.com/ https://divinglaravel.com/cost-performance-optimization-in-laravel-vapor
And the course by Jonathan https://eloquent-course.reinink.ca/ it also helped. He has been posting about database performance for a while and you should stalk his tweets because you'll definitely find a lot of information.
And also, I highly recommend his course.
And also, I highly recommend his course.
I put this whole "advertisement" on top because this people were directly involved as you might notice. But let me say what I did to improve the performance.
Reviewed all queries. I was running on Vapor (which can upload directly to S3) with a N+1 issue on a media model. Don't be that stupid. Indexes, relations, the evil $with, etc. Cached some queries that doesn't change often.
I stored some data on Vuex and stop unnecessary requests between route change (it's a SPA). In my case, I was fetching data every time user enters in the page and this wasn't necessary. The basic optimizations steps: Route and config caching
Laravel Vapor is just a joy to use and easy to getting up & running. You do have to take some considerations, but it's definitely worth it and you can deploy projects very quickly and without headaches managing servers. 
