Issue #10628 has been updated by Guo Xiang Tan.


Eric Wong wrote:
> tgx_world: Please don't use screenshots when a few words explaining the
>  situation will do.  Not everyone can view pics: lack of working GUI,
>  poor eyesight or danger of opening inappropriate images in public areas.
>  
>  Fortunately, I was able to open the link to see the issue was with
>  the bm_app_uri benchmark being slower.
>  
>  I tried some optimizations, but it's still slower than 2.1.5 on my
>  Haswell E3-1230 v3 server:
>  
>    http://80x24.org/spew/m/ugly-uri-optimizations / r48922.txt
>  
>  Unfortunately, these make evaluating effects of any future compile.c
>  optimizations more difficult.
>  
>  benchmark results:
>  minimum results in each 10 measurements.
>  Execution time (sec)
>  name	2.1.5	trunk	built
>  app_uri	0.484	0.584	0.500
>  
>  Speedup ratio: compare with the result of `2.1.5' (greater is better)
>  name	trunk	built
>  app_uri	0.829	0.968
>  
>  naruse: any thoughts?

Opps got it. I'll try to explain better in words next time.

----------------------------------------
misc #10628: Peformance of URI module
https://bugs.ruby-lang.org/issues/10628#change-50569

* Author: Guo Xiang Tan
* Status: Open
* Priority: Normal
* Assignee: Yui NARUSE
* Category: 
* Target version: 
----------------------------------------
Please view attached screenshot or go to [the following link](https://railsbench.herokuapp.com/tgxworld/ruby?utf8=%E2%9C%93&result_types%5B%5D=app_uri&commit=Submit) to see benchmark graph over time.

It got slower after this [commit](https://github.com/ruby/ruby/commit/bb83f32dc3e0424d25fa4e55d8ff32b061320e41).

Hope this helps.

---Files--------------------------------
Screenshot from 2014-12-21 22_41_39.png (63.5 KB)


-- 
https://bugs.ruby-lang.org/