app_profiler
Ruby Tests Profiling Toolbox
| app_profiler | Ruby Tests Profiling Toolbox | |
|---|---|---|
| 2 | 7 | |
| 196 | 1,793 | |
| 2.0% | 0.6% | |
| 7.1 | 7.8 | |
| 3 days ago | 6 days ago | |
| Ruby | Ruby | |
| MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
app_profiler
-
Performance Profiling a Mongoid Issue Using AppProfiler
While doing research on Ruby profiling I found Shopify's blog post on "How to Fix Slow Code in Ruby". Though the entire post was extremely insightful, it lead me to Shopify's app_profiler library, which can be used to automatically profile code and redirect the output to a local instance of speedscope. Having worked previously with Flame Graphs of CPU stack traces collected using perf.
- Five tools for profiling Rails apps
Ruby Tests Profiling Toolbox
-
Must-have gems for mature Rails
gem "test-prof" - https://github.com/test-prof/test-prof | Toolkit for inspecting and optimising your test-suite, a must-have.
-
Measuring load time on fixtures
You might be able to do something with https://test-prof.evilmartians.io, but I'm not sure it has anything specific to fixtures out of the box. Maybe using the event profiler on sql.active_record events would be close enough. In the limit, you could wire together your own ActiveSupport::Notifications.instrument around the relevant blocks + an ActiveSupport::Notifications.subscribe to that event so as to log the relevant information. Docs: https://api.rubyonrails.org/classes/ActiveSupport/Notifications.html
-
How to optimize factory creation.
To have a better vision of what objects are created in our spec file we can use test-prof, a powerful gem that provides a collection of different tools to analyse your test suite performance. One of this tool is really useful to identify a factory cascade, let’s introduce factory profiler.
-
A Trick For Reading Flamegraphs
TestProf can be used to get flamegraphs for Ruby test suites.
- How to improve a test suit made with Rspec, Capybara, FactoryBot and Siteprism
-
Does pytest break a lot of coding rules?
Rspec has spec_helper.rb.
-
Learning resources to broaden the knowledge
I also love the test-prof documentation, there's a lot of good ideas on how to improve test performance.
What are some alternatives?
speedscope - 🔬 A fast, interactive web-based viewer for performance profiles.
DuckRails - Development tool to mock API endpoints quickly and easily (docker image available)
FlameGraph - Stack trace visualizer
Spinach - Spinach is a BDD framework on top of Gherkin.
prosopite - :mag: Rails N+1 queries auto-detection with zero false positives / false negatives
minitest - minitest provides a complete suite of testing facilities supporting TDD, BDD, mocking, and benchmarking.
timecop - A gem providing "time travel", "time freezing", and "time acceleration" capabilities, making it simple to test time-dependent code. It provides a unified method to mock Time.now, Date.today, and DateTime.now in a single call.
factory_bot - A library for setting up Ruby objects as test data.
faker - A library for generating fake data such as names, addresses, and phone numbers.
Watir - Watir Powered By Selenium
Cucumber - A home for issues that are common to multiple cucumber repositories
ffaker - Faker refactored.