rails_panel VS laravel-debugbar

This seems pretty similar to https://github.com/dejan/rails_panel. Was that your inspiration?

There's a few things that could be happening. I recommend trying out https://github.com/dejan/rails_panel. It gives you a better break down if exactly what's taking time. You also might look at how long it takes to actually instantiate your models. The actual query time is usually the slowest operation, but if you have a bunch of models on the page just the classes being loaded can take a good amount of time

Love seeing the set of gems that folks tend to bring into all their projects. https://github.com/dejan/rails_panel Was a new one for me, will def be checking that out

Laravel Debugbar: Laravel Debugbar is a package that integrates PHP Debug Bar with Laravel. It provides a convenient toolbar that sits at the bottom of your application's pages and offers insights into various aspects of your application, including database queries, route information, views, events, and more. With its customizable configuration options and extensive feature set, Laravel Debugbar is an excellent choice for monitoring database queries and debugging your Laravel applications.

debugbar And n+1 query

tldr using debugbar is a good point, everything else is just use laravel when using laravel and avoid n+1 problem

Nice but I can get the same functionality with the debugbar - what makes this better?

We then used platform-specific performance analysis tools to determine which of these endpoints needed the most attention. The highest-traffic sites we needed to optimize used Laravel, a popular PHP framework. We used Laravel Debugbar to analyze those web apps.

Try installing laravel-debugbar, it will show you which parts of the app are slow (e.g. boot up vs views), which queries are slow, and how many queries run (helpful when you forgot to eager load some models).

I wanted to tweak Laravel Debugbar, so it could also work with any JSON API, but I ended up writing a minimal package of my own to do the trick.