# GSOC 2017 - Long Running Ruby and Rails Benchmarks

**URL:** <https://community.rubybench.org/t/gsoc-2017-long-running-ruby-and-rails-benchmarks/130>\
**Category:** Uncategorized\
**Created:** [March 23, 2017, 9:35am UTC](https://community.rubybench.org/t/gsoc-2017-long-running-ruby-and-rails-benchmarks/130 "2017-03-23T09:35:27Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![sam](https://sea2.discourse-cdn.com/flex016/user_avatar/community.rubybench.org/sam/32/5_2.png) [@sam](https://community.rubybench.org/u/sam)\
**Post date:** [April 3, 2017, 12:57pm UTC](https://community.rubybench.org/t/gsoc-2017-long-running-ruby-and-rails-benchmarks/130/3 "2017-04-03T12:57:28Z")

</div>

> [@GSOC Project : Improving RubyBench](http://community.rubybench.org/t/gsoc-project-improving-rubybench/99/7):
>
> Note, just going to mention this here. I think the bisecting stuff is very interesting and important, however feel that the most important thing is getting our benchmarks in order. I feel there is a huge gap around our Rails benchmarks, in particular have a look at say: [https://rubybench.org/rails/rails/commits?result\_type=activerecord/mysql2\_scope\_all\_with\_default\_scope&display\_count=200](https://rubybench.org/rails/rails/commits?result_type=activerecord/mysql2_scope_all_with_default_scope&display_count=200) What if this was implemented raw against the mysql gem, how fast would it be? How many objects would b…

to me is still the #1 #2 and #3 issues I want sorted, our benchmarks are not honest enough, there is no way to tell how much performance is being left on the table.

---

_[View the full topic](https://community.rubybench.org/t/gsoc-2017-long-running-ruby-and-rails-benchmarks/130)._