Skip to content

GitLab

Switch branch/tag
  1. 05 Feb, 2016 1 commit
  3. 03 Feb, 2016 4 commits
  5. 28 Jan, 2016 2 commits
  7. 27 Jan, 2016 2 commits
  9. 22 Jan, 2016 3 commits
  11. 21 Jan, 2016 1 commit
  13. 19 Jan, 2016 1 commit
  15. 28 Dec, 2015 1 commit
  17. 11 Dec, 2015 1 commit
  19. 09 Dec, 2015 5 commits
  21. 23 Nov, 2015 3 commits
  23. 17 Nov, 2015 1 commit
  25. 16 Nov, 2015 2 commits
  27. 13 Nov, 2015 1 commit
  29. 11 Nov, 2015 2 commits
  31. 10 Nov, 2015 1 commit
  33. 05 Oct, 2015 1 commit
  35. 02 Oct, 2015 1 commit
    • Yorick Peterse's avatar
      Basic setup for an RSpec based benchmark suite · 19893a1c
      Yorick Peterse authored 
      This benchmark suite uses benchmark-ips
(https://github.com/evanphx/benchmark-ips) behind the scenes. Specs can
be turned into benchmark specs by setting "benchmark" to "true" in the
top-level describe block like so:

    describe SomeClass, benchmark: true do

    end

Writing benchmarks can be done using custom RSpec matchers, for example:

    describe MaruTheCat, benchmark: true do
      describe '#jump_in_box' do
        it 'should run 1000 iterations per second' do
          maru = described_class.new

          expect { maru.jump_in_box }.to iterate_per_second(1000)
        end
      end
    end

By default the "iterate_per_second" expectation requires a standard
deviation under 30% (this is just an arbitrary default for now). You can
change this by chaining "with_maximum_stddev" on the expectation:

    expect { maru.jump_in_box }.to iterate_per_second(1000)
      .with_maximum_stddev(10)

This will change the expectation to require a maximum deviation of 10%.

Alternatively you can use the it block style to write specs:

    describe MaruTheCat, benchmark: true do
      describe '#jump_in_box' do
        subject { -> { described_class.new } }

        it { is_expected.to iterate_per_second(1000) }
      end
    end

Because "iterate_per_second" operates on a block, opposed to a static
value, the "subject" method must return a Proc. This looks a bit goofy
but I have been unable to find a nice way around this.
      19893a1c
  37. 10 Sep, 2015 1 commit
  39. 09 Sep, 2015 1 commit
  41. 28 Jun, 2015 1 commit
  43. 23 Jun, 2015 1 commit
  45. 18 Jun, 2015 2 commits
  47. 17 Jun, 2015 1 commit