Using Eloquent for performance design patterns

Transcript

1. Using Eloquent for performance design patterns Nemanja Marić maki10
2. About me • PHP Developer at Abstract • Member of PHP Serbia Community • Co-organizer Laravel Serbia Meetup’s • Working with PHP since 2014 • In Laravel world from 2016 • Open source contributor • Contributing to the Laravel Framework • And most !important: Husband and father of two little angels
3. Interesting part Share your knowledge with others to get some knowledge.
4. Over the years
5. Everything we need is: Laravel debugbar, reinink/advanced-eloquent < Laravel 6
6. Let’s start
8. Run super fast
10. Proudly generate with beyondcode/laravel -er-diagram-generat or
11. Requirement number 1 For logged user show only results where club is matched and his buddies.
12. Add UserPolicy - php artisan make:policy UserPolicy
13. It’s work. Let’s see debugbar
14. But why? Queries are super fast, but why is memory and execution time so big and what is this last 1012 models? Does someone know?
15. Answer Because we do to much jobs in PHP and not in database. 1012 Models are custom metric in debugbar added by @reinink (Jonathan Reinink), is available from v3.2.6, it’s called “Hydrated Models” “It provides a quick count of how many Eloquent models were created during a request...which can have a huge impact on performance.“
16. Let’s fix issue
17. Rerun, and we are good to go further
18. Requirement number 2 Order table data in two way: 1. Order by buddies first 2. Order by name
19. This is heavy because we need to order by Pivot table. Everyone who sorted results like this knows that is this very heavy, unless? Order by buddies first, why is heavy?
20. Order by custom query function `orderBySub`
21. Query builder custom macro
22. Order First By Buddies then name
24. Perfect
25. Requirement number 3 Add last trip date.
26. Add last trip date, hmm?
27. Peace of cake
29. Wow, hmm, ok ok I forgot eager load
30. Oh 250 000 trips results show faces and punch back
31. Let’s force N+1. N+1 is not always worst choice
32. N+1 cost less resources. So is it better? Can be better?
33. Yes via custom builder function `addSubSelect`
34. We need to tweak a bit
36. We are back in business
37. Requirement number 4 Add last trip lake
38. Add withLastTripLake scope
40. No impact on performance at all
41. Requirement number 5 Let’s make last trip clickable so we can go to actual trip.
42. Stop for second
43. Let’s add dynamic property
44. Remember?
46. Replace old scopes
48. Super easy, super fast
49. Questions? Leave review: https://joind.in/user/maki10 Slides: https://speakerdeck.com/maki10 Twitter: https://twitter.com/NemanjaMaki10 All credits go to @reinink and his Laracon 2019 talk. Watch him on Laracon2019 was very good choice, and it’s my advice for you to watch when he kicking a stage.