meta_profiler 0.0.1

data/Gemfile

@@ -0,0 +1,4 @@
+source 'https://rubygems.org'
+
+# Specify your gem's dependencies in meta_profiler.gemspec
+gemspec

data/LICENSE

@@ -0,0 +1,22 @@
+Copyright (c) 2012 Joe Fredette
+
+MIT License
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/README.md

@@ -0,0 +1,44 @@
+# MetaProfiler
+
+`meta_profiler` provides a single interface to profile small chunks of code across different ruby implementations.
+Presently, it supports Rubinius, JRuby, and MRI > 1.9.2. It may support older MRIs, but they have not yet been tested.
+
+This tool was extracted from a script I used to keep lying around in my home directory to help when trying to settle
+debates about whether something was faster or slower, the easiest way to run a profile is simply to install this gem,
+require it, and write your code in a `profile { #code }` block, simply running your desired version of ruby on that
+script will then automatically print profiling results to STDOUT.
+
+Future plans include:
+
+* providing a consistent report style for all implementations
+* better testing (I told you it was extracted from a throwaway script, right?)
+* less procedural implementation
+* better documentation
+* include memory profiling as an option, etc.
+
+
+## Installation
+
+Add this line to your application's Gemfile:
+
+    gem 'meta_profiler'
+
+And then execute:
+
+    $ bundle
+
+Or install it yourself as:
+
+    $ gem install meta_profiler
+
+## Usage
+
+TODO: Write usage instructions here
+
+## Contributing
+
+1. Fork it
+2. Create your feature branch (`git checkout -b my-new-feature`)
+3. Commit your changes (`git commit -am 'Added some feature'`)
+4. Push to the branch (`git push origin my-new-feature`)
+5. Create new Pull Request

data/Rakefile

@@ -0,0 +1,2 @@
+#!/usr/bin/env rake
+require "bundler/gem_tasks"

data/lib/meta_profiler.rb

@@ -0,0 +1,2 @@
+require "meta_profiler/version"
+require 'meta_profiler/profile'

data/lib/meta_profiler/profile.rb

@@ -0,0 +1,101 @@
+require 'rubygems'
+
+#class MetaProfiler
+  #def initialize(opts)
+    #@use_gc = opts.delete(:no_gc)
+    #@title = opts.delete(:title)
+    #@printer = opts.delete(:printer) || 
+    #@times_to_execute = opts.delete(:times_to_execute)
+  #end
+
+  #def profile
+    #load_profiler!
+    #results = run_profile do
+      #yield
+    #end
+    #printer.print(results)
+  #end
+
+  #private
+
+  #attr_reader :times_to_execute, :title, :printer
+
+  #def gc?
+    #!@use_gc
+  #end
+
+  #def run_profile
+    #if @profiler_needs_false
+      #@profiler.profile(false) do
+        #yield
+      #end
+    #else
+      #@profiler.profile do
+        #yield
+      #end
+    #end
+  #end
+
+  #def load_profiler!
+    #if defined?(Rubinius)
+      #require 'profiler'
+      #@profiler = Rubinius::Profiler::Instrumenter.new
+      #@profiler_needs_false = true
+    #elsif defined?(JRuby)
+      #require 'jruby/profiler'
+      #@profiler = JRuby::Profiler
+    #else
+      #require 'ruby-prof'
+      #@profiler = RubyProf
+    #end
+  #end
+#end
+
+
+def profile_rubinius_style(opts)
+  require 'profiler'
+  profiler = Rubinius::Profiler::Instrumenter.new
+
+  profiler.profile do
+    1_000_000.times do
+      yield
+    end
+  end
+end
+
+def profile_rubyprof_style(opts)
+  require 'ruby-prof'
+  result = RubyProf.profile do
+    1_000_000.times do 
+      yield
+    end
+  end
+  printer = RubyProf::FlatPrinter.new(result)
+  printer.print(STDOUT)
+end
+
+def profile_java_style(opts)
+  require 'jruby/profiler'
+  profile_data = JRuby::Profiler.profile do
+    yield 
+  end
+
+  profile_printer = JRuby::Profiler::FlatProfilePrinter.new(profile_data)
+  profile_printer.printProfile(STDOUT)
+end
+
+def profile(title = nil, opts = {})
+  GC.disable if opts[:no_gc]
+  puts title if title
+
+  if defined?(Rubinius)
+    profile_rubinius_style(opts)
+  elsif defined?(JRuby)
+    profile_java_style(opts)
+  else
+    profile_rubyprof_style(opts)
+  end
+
+  puts "--------------------------------------------------------------------------------"
+  GC.enable if opts[:no_gc]
+end

data/lib/meta_profiler/version.rb

@@ -0,0 +1,3 @@
+module MetaProfiler
+  VERSION = "0.0.1"
+end

data/meta_profiler.gemspec

@@ -0,0 +1,29 @@
+# -*- encoding: utf-8 -*-
+require File.expand_path('../lib/meta_profiler/version', __FILE__)
+
+Gem::Specification.new do |gem|
+  gem.authors       = ["Joe Fredette"]
+  gem.email         = ["jfredett@gmail.com"]
+  gem.description   = %q{Abstracts over the interfaces to the various implementation-specific profiling tools}
+  gem.summary       = %q{
+   meta_profiler provides a single interface to profile small chunks of code across different ruby implementations.
+   Presently, it supports Rubinius, JRuby, and MRI > 1.9.2. It may support older MRIs, but they have not yet been tested.
+
+   This tool was extracted from a script I used to keep lying around in my home directory to help when trying to settle 
+   debates about whether something was faster or slower, the easiest way to run a profile is simply to install this gem,
+   require it, and write your code in a `profile { #code }` block, simply running your desired version of ruby on that
+   script will then automatically print profiling results to STDOUT.
+  }
+  gem.homepage      = "http://github.com/jfredett/meta_profiler"
+
+  if not (defined? Rubinius or defined? JRuby)
+    gem.add_dependency 'ruby-prof'
+  end
+
+  gem.files         = `git ls-files`.split($\)
+  gem.executables   = gem.files.grep(%r{^bin/}).map{ |f| File.basename(f) }
+  gem.test_files    = gem.files.grep(%r{^(test|spec|features)/})
+  gem.name          = "meta_profiler"
+  gem.require_paths = ["lib"]
+  gem.version       = MetaProfiler::VERSION
+end

metadata

@@ -0,0 +1,62 @@
+--- !ruby/object:Gem::Specification
+name: meta_profiler
+version: !ruby/object:Gem::Version
+  prerelease: 
+  version: 0.0.1
+platform: ruby
+authors:
+- Joe Fredette
+autorequire: 
+bindir: bin
+cert_chain: []
+date: 2012-09-24 00:00:00.000000000 Z
+dependencies: []
+description: Abstracts over the interfaces to the various implementation-specific
+  profiling tools
+email:
+- jfredett@gmail.com
+executables: []
+extensions: []
+extra_rdoc_files: []
+files:
+- Gemfile
+- LICENSE
+- README.md
+- Rakefile
+- lib/meta_profiler.rb
+- lib/meta_profiler/profile.rb
+- lib/meta_profiler/version.rb
+- meta_profiler.gemspec
+homepage: http://github.com/jfredett/meta_profiler
+licenses: []
+post_install_message: 
+rdoc_options: []
+require_paths:
+- lib
+required_ruby_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ! '>='
+    - !ruby/object:Gem::Version
+      version: '0'
+  none: false
+required_rubygems_version: !ruby/object:Gem::Requirement
+  requirements:
+  - - ! '>='
+    - !ruby/object:Gem::Version
+      version: '0'
+  none: false
+requirements: []
+rubyforge_project: 
+rubygems_version: 1.8.24
+signing_key: 
+specification_version: 3
+summary: ! 'meta_profiler provides a single interface to profile small chunks of code
+  across different ruby implementations. Presently, it supports Rubinius, JRuby, and
+  MRI > 1.9.2. It may support older MRIs, but they have not yet been tested.  This
+  tool was extracted from a script I used to keep lying around in my home directory
+  to help when trying to settle  debates about whether something was faster or slower,
+  the easiest way to run a profile is simply to install this gem, require it, and
+  write your code in a `profile { #code }` block, simply running your desired version
+  of ruby on that script will then automatically print profiling results to STDOUT.'
+test_files: []
+has_rdoc: