MemoryProfiler VS prosopite

Wire the memory_profiler into an around_action to identify your bloaty actions.

The memory_profiler gem offers a very simple API and a detailed (albeit a little overwhelming) allocated and retained memory report — that includes the classes of objects that are allocated, their size, and where they were allocated. It's straightforward to add to our leaky program.

memory_profiler

We don't need to rely upon a priori reasoning only, we can use memory_profiles and benchmark_ips to compare the memory consumption and iterations per second of each solution.

Either https://github.com/tmm1/stackprof for cpu or https://github.com/SamSaffron/memory_profiler for memory. In practice profiling and removing allocations also gives a large perf boost.

Our project has one endpoint which gets called quite often. So, I profiled it with memory profiler and saw a line pointing to hstore.rb.

The new option is called Prosopite.min_n_queries: https://github.com/charkost/prosopite

N+1 requests are an easy first step. Bullet gem works, but is overeager. I prefer Prosopite for this task (https://github.com/charkost/prosopite)

I first posted prosopite in this subreddit a year ago as an alternative to bullet.

A recent n+1 tool is Prospite. It was released a couple of weeks ago so it's not been written about it ...