# RubyBench weekly report

**URL:** <https://community.rubybench.org/t/rubybench-weekly-report/43>\
**Category:** Uncategorized\
**Created:** [March 4, 2015, 1:17am UTC](https://community.rubybench.org/t/rubybench-weekly-report/43 "2015-03-04T01:17:33Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/rubybench/original/1X/4ae23b7eff9a1b039e126f05dd734ab09c8ab4b5.png) [@system](https://community.rubybench.org/u/system)\
**Post date:** [March 4, 2015, 1:17am UTC](https://community.rubybench.org/t/rubybench-weekly-report/43/1 "2015-03-04T01:17:33Z")

</div>

We’ll like to allow people to subscribe and unsubscribe to a weekly report to view all the benchmark results.

Things to tie down:

- Report format

---

<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:** [March 4, 2015, 1:26am UTC](https://community.rubybench.org/t/rubybench-weekly-report/43/2 "2015-03-04T01:26:21Z")

</div>

I think version 0 should be pretty simple.

Walk through all the be benches - if any bench got faster or slower beyond a threashold, include a link to it with details EG:

### The following benchmarks got faster

- app\_answer - 2% faster - link to report

### The following benchmarks got slower

- app\_mandelbrot - 2% slower - link to report

* * *

If nothing changed no need to send an email, we need to be super careful we only alert when there is a material change and it is not purely “noise”

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/rubybench/original/1X/4ae23b7eff9a1b039e126f05dd734ab09c8ab4b5.png) [@system](https://community.rubybench.org/u/system)\
**Post date:** [March 13, 2015, 2:31pm UTC](https://community.rubybench.org/t/rubybench-weekly-report/43/3 "2015-03-13T14:31:17Z")

</div>

![](https://sea2.discourse-cdn.com/flex016/uploads/rubybench/27/aaddbd2b7b0830f3.png)

Noticed this today which was due to one of the commits which was fixed by the commit right after.

TODO: We need a good way of identifying/filtering anomalies like this in order to prevent false positives

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/rubybench/original/1X/4ae23b7eff9a1b039e126f05dd734ab09c8ab4b5.png) [@system](https://community.rubybench.org/u/system)\
**Post date:** [March 18, 2015, 1:06pm UTC](https://community.rubybench.org/t/rubybench-weekly-report/43/4 "2015-03-18T13:06:33Z")

</div>

> [@system](#):
>
> Noticed this today which was due to one of the commits which was fixed by the commit right after.
> 
> TODO: We need a good way of identifying/filtering anomalies like this in order to prevent false positives

Confirmed that this was caused by a commit made accidentally. I think the way we should handle this is to just invalidate the particular commit in the future.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/rubybench/original/1X/4ae23b7eff9a1b039e126f05dd734ab09c8ab4b5.png) [@system](https://community.rubybench.org/u/system)\
**Post date:** [May 28, 2015, 3:54am UTC](https://community.rubybench.org/t/rubybench-weekly-report/43/5 "2015-05-28T03:54:12Z")

</div>

We need something like this 😁

> <https://twitter.com/tomdale/status/603725605146853377>

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/rubybench/original/1X/4ae23b7eff9a1b039e126f05dd734ab09c8ab4b5.png) [@system](https://community.rubybench.org/u/system)\
**Post date:** [May 28, 2015, 3:55am UTC](https://community.rubybench.org/t/rubybench-weekly-report/43/6 "2015-05-28T03:55:56Z")

</div>

Relevant information for the future [mir.aculo.us JavaScript with Thomas Fuchs » Blog Archive » Embedding Canvas and SVG charts in emails](http://mir.aculo.us/2013/04/30/embed-canvas-and-svg-charts-in-emails/)