Thanks for doing this. Ideas: - Rails ActiveRecord SQL debugging (eager loading and N+1 problems - how to spot them) - how we configure passenger by default and what are the limitations - how passenger handles memory-leaked processes (it doesn't - see my script) - how to enable slow SQL logging on PostgreSQL - drop a word about foreman-trace perhaps - utilizing information from Satellite 6 performance tuning guide
LLZ On Tue, May 9, 2017 at 4:49 PM, Christopher Duryee <[email protected]> wrote: > > > On Tue, May 9, 2017 at 9:01 AM, <[email protected]> wrote: >> >> Hey, I want to do a performance analysis deep-dive. >> >> What I had in mind: >> >> 1. Installation of tooling in development environment >> 2. Simple request breakdown (view, sql) >> 3. Debugging API request >> 4. Time graph (flamegraph) >> 5. Memory consumption >> 6. Installation in prod env >> 7. Analyzing POST requests >> >> Feel free to ask questions and suggest topics that you want me to cover. > > > This list looks good, thanks for covering it. Can you also add how to check > if a foreman instance is maxed out on passenger workers via > passenger-status? > >> >> >> Shim. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "foreman-dev" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/d/optout. > > > -- > You received this message because you are subscribed to the Google Groups > "foreman-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- Later, Lukas @lzap Zapletal -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
