===========================================================
.___ __ __
_________________ __ __ __| _/|__|/ |_
/ ___\_` __ \__ \ | | \/ __ | | \\_ __\
/ /_/ > | \// __ \| | / /_/ | | || |
\___ /|__| (____ /____/\____ | |__||__|
/_____/ \/ \/
grep rough audit - static analysis tool
v2.8 written by @Wireghoul
=================================[justanotherhacker.com]===
ruby-derailed-benchmarks-1.7.0/CHANGELOG.md-100-
ruby-derailed-benchmarks-1.7.0/CHANGELOG.md:101:- Added `derailed` command line utility. Can be used with just a Gemfile using command `$ derailed bundle:mem` and `$ derailed bundle:objects`. All existing Rake tasks can now be called with `$ derailed exec` such as `$ derailed exec perf:mem`.
ruby-derailed-benchmarks-1.7.0/CHANGELOG.md-102-- Changed memory_profiler task to be `perf:objects` instead of `perf:mem`.
##############################################
ruby-derailed-benchmarks-1.7.0/lib/derailed_benchmarks/tasks.rb-283- puts ""
ruby-derailed-benchmarks-1.7.0/lib/derailed_benchmarks/tasks.rb:284: puts "Run `$ heapy --help` for more options"
ruby-derailed-benchmarks-1.7.0/lib/derailed_benchmarks/tasks.rb-285- puts ""
##############################################
ruby-derailed-benchmarks-1.7.0/README.md-31-
ruby-derailed-benchmarks-1.7.0/README.md:32:Then run `$ bundle install`.
ruby-derailed-benchmarks-1.7.0/README.md-33-
##############################################
ruby-derailed-benchmarks-1.7.0/README.md-51-
ruby-derailed-benchmarks-1.7.0/README.md:52:All commands in this section will begin with `$ derailed bundle:`
ruby-derailed-benchmarks-1.7.0/README.md-53-
##############################################
ruby-derailed-benchmarks-1.7.0/README.md-144-
ruby-derailed-benchmarks-1.7.0/README.md:145:Once you identify a gem that creates a large amount of memory using `$ bundle exec derailed bundle:mem` you can pull that gem into it's own Gemfile and run `$ bundle exec derailed bundle:objects` to get detailed information about it. This information can be used by contributors and library authors to identify and eliminate object creation hotspots.
ruby-derailed-benchmarks-1.7.0/README.md-146-
##############################################
ruby-derailed-benchmarks-1.7.0/README.md-158-
ruby-derailed-benchmarks-1.7.0/README.md:159:This benchmarking will attempt to boot your Rails app and run benchmarks against it. Unlike the static benchmarking with `$ bundle exec derailed bundle:*` these will include information about your specific app. The pro is you'll get more information and potentially identify problems in your app code, the con is that it requires you to be able to boot and run your application in a `production` environment locally, which for some apps is non-trivial.
ruby-derailed-benchmarks-1.7.0/README.md-160-
##############################################
ruby-derailed-benchmarks-1.7.0/README.md-198-
ruby-derailed-benchmarks-1.7.0/README.md:199:You can run commands against your app by running `$ derailed exec`. There are sections on setting up Rack and using authenticated requests below. You can see what commands are available by running:
ruby-derailed-benchmarks-1.7.0/README.md-200-
##############################################
ruby-derailed-benchmarks-1.7.0/README.md-272-
ruby-derailed-benchmarks-1.7.0/README.md:273:This is similar to `$ bundle exec derailed bundle:objects` however it includes objects created at runtime. It's much more useful for actual production performance debugging, the other is more useful for library authors to debug.
ruby-derailed-benchmarks-1.7.0/README.md-274-
##############################################
ruby-derailed-benchmarks-1.7.0/README.md-302-
ruby-derailed-benchmarks-1.7.0/README.md:303:Ruby memory typically goes in one direction, up. If your memory is large when you boot the application it will likely only increase. In addition to debugging memory retained from dependencies obtained while running `$ derailed bundle:mem` you'll likely want to see how your own files contribute to memory use.
ruby-derailed-benchmarks-1.7.0/README.md-304-
##############################################
ruby-derailed-benchmarks-1.7.0/README.md-321-
ruby-derailed-benchmarks-1.7.0/README.md:322:If your application code is extremely large at boot consider using `$ derailed exec perf:objects` to debug low level object creation.
ruby-derailed-benchmarks-1.7.0/README.md-323-
##############################################
ruby-derailed-benchmarks-1.7.0/README.md-582-
ruby-derailed-benchmarks-1.7.0/README.md:583:To find out the tasks available you can use `$ rake -f perf.rake -T` which essentially says use the file `perf.rake` and list all the tasks.
ruby-derailed-benchmarks-1.7.0/README.md-584-
##############################################
ruby-derailed-benchmarks-1.7.0/README.md-687-
ruby-derailed-benchmarks-1.7.0/README.md:688:Most of the commands are wrappers around other libraries, go check them out. Also thanks to [@tenderlove](https://twitter.com/tenderlove) as I cribbed some of the Rails init code in `$ rake perf:setup` from one of his projects.
ruby-derailed-benchmarks-1.7.0/README.md-689-