# Discourse Releases benchmarks bumped to Discourse stable 1.2.4 **URL:** \ **Category:** Uncategorized\ **Created:** [June 2, 2015, 8:58am UTC](https://community.rubybench.org/t/discourse-releases-benchmarks-bumped-to-discourse-stable-1-2-4/73 "2015-06-02T08:58:43Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/rubybench/original/1X/4ae23b7eff9a1b039e126f05dd734ab09c8ab4b5.png) [@system](https://community.rubybench.org/u/system)\ **Post date:** [June 2, 2015, 8:58am UTC](https://community.rubybench.org/t/discourse-releases-benchmarks-bumped-to-discourse-stable-1-2-4/73/1 "2015-06-02T08:58:43Z")
I just fixed Discourse benchmarks and we’re now benchmarking against Discourse stable 1.2.4. Currently, only releases benchmarks have been updated. I’ve also removed Discourse’s per-commit benchmarks as they are outdated. @sam I’m thinking of only running nightly bench for Discourse instead of on a per commit basis. Each Discourse benchmark takes too long to run partly due to `bundle install`. WDYT? ---
**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:** [June 2, 2015, 3:10pm UTC](https://community.rubybench.org/t/discourse-releases-benchmarks-bumped-to-discourse-stable-1-2-4/73/2 "2015-06-02T15:10:57Z")
Nightly is fine, no problems there. ---
**Author:** ![noahgibbs](https://sea2.discourse-cdn.com/flex016/user_avatar/community.rubybench.org/noahgibbs/32/91_2.png) [@noahgibbs](https://community.rubybench.org/u/noahgibbs)\ **Post date:** [March 29, 2017, 11:49pm UTC](https://community.rubybench.org/t/discourse-releases-benchmarks-bumped-to-discourse-stable-1-2-4/73/3 "2017-03-29T23:49:43Z")
Hey, folks. Was just noticing that the Discourse version and accompanying Ruby version were locked at 2015. Any plans to bump the Discourse or Ruby version for the benchmark? ---
**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/rubybench/original/1X/4ae23b7eff9a1b039e126f05dd734ab09c8ab4b5.png) [@system](https://community.rubybench.org/u/system)\ **Post date:** [April 3, 2017, 12:53am UTC](https://community.rubybench.org/t/discourse-releases-benchmarks-bumped-to-discourse-stable-1-2-4/73/4 "2017-04-03T00:53:08Z")
Yup it has been on my list for awhile to bump the benchmark and make it working again. We’ll likely do so soon once we get Discourse upgraded to Rails 5. ---
**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, 1:00pm UTC](https://community.rubybench.org/t/discourse-releases-benchmarks-bumped-to-discourse-stable-1-2-4/73/5 "2017-04-03T13:00:43Z")
the big thing that is blocking us is sprockets, recently I have been eliminating sprockets from our CSS pipeline which should make it quite a bit easier to upgrade to latest sprockets. Without an upgrade to sprockets 4 we are stuck on Ruby 2.3 cause of a cascade of dependencies. Recently when Sean Griffin looked at a sprockets upgrade it seemed to add a fair amount of memory to the precompile step, which was unacceptable for all the self hosters that are already riding on the edge of out-of-memory. ---
**Author:** ![noahgibbs](https://sea2.discourse-cdn.com/flex016/user_avatar/community.rubybench.org/noahgibbs/32/91_2.png) [@noahgibbs](https://community.rubybench.org/u/noahgibbs)\ **Post date:** [April 4, 2017, 4:10pm UTC](https://community.rubybench.org/t/discourse-releases-benchmarks-bumped-to-discourse-stable-1-2-4/73/6 "2017-04-04T16:10:10Z")
That makes sense. Thanks for letting me know! I’ve been working on a Discourse-based Rails benchmark, and of course the Ruby 2.4 thing is being a bit of a hangup 🙂 ---
**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 23, 2017, 2:25pm UTC](https://community.rubybench.org/t/discourse-releases-benchmarks-bumped-to-discourse-stable-1-2-4/73/7 "2017-04-23T14:25:05Z")
BTW… sprockets is no longer blocking us, now that I ripped out all of the stylesheet precompilation and started doing it myself. We are running 2.4 in production on some systems now!