[#85349] [Ruby trunk Bug#14334] Segmentation fault after running rspec (ruby/2.5.0/erb.rb:885 / simplecov/source_file.rb:85) — pragtob@...
Issue #14334 has been updated by PragTob (Tobias Pfeiffer).
3 messages
2018/02/02
[#85358] Re: [ruby-cvs:69220] nobu:r62039 (trunk): compile.c: unnecessary freezing — Eric Wong <normalperson@...>
[email protected] wrote:
5 messages
2018/02/03
[#85612] Why require autoconf 2.67+ — leam hall <leamhall@...>
Please pardon the intrusion; I am new to Ruby and like to pull the
6 messages
2018/02/17
[#85616] Re: Why require autoconf 2.67+
— Vít Ondruch <v.ondruch@...>
2018/02/18
VGhpcyBjb3VsZCBoZWxwIHlvdSB0byBidWlsZCBSdWJ5IHdpdGggb2xkZXIgYXV0b2NvbmYgKDIu
[#85634] [Ruby trunk Bug#14494] [PATCH] tool/m4/ruby_replace_type.m4 use AC_CHECK_TYPES for HAVE_* macros — normalperson@...
Issue #14494 has been reported by normalperson (Eric Wong).
3 messages
2018/02/19
[#85674] [Ruby trunk Feature#13618] [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid — matz@...
Issue #13618 has been updated by matz (Yukihiro Matsumoto).
5 messages
2018/02/20
[#85686] Re: [Ruby trunk Feature#13618] [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid
— Eric Wong <normalperson@...>
2018/02/20
[email protected] wrote:
[#85704] Re: [Ruby trunk Feature#13618] [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid
— Koichi Sasada <ko1@...>
2018/02/21
On 2018/02/20 18:06, Eric Wong wrote:
[ruby-core:85629] [Ruby trunk Bug#14490] MJIT slows down Rails applications
From:
takashikkbn@...
Date:
2018-02-19 02:38:12 UTC
List:
ruby-core #85629
Issue #14490 has been updated by k0kubun (Takashi Kokubun). > This was reported earlier but I would like to add some test methodology here: (tested using Discourse) Ah, somehow I didn't read this part. Thank you for sharing! I'm using the similar way. ---------------------------------------- Bug #14490: MJIT slows down Rails applications https://bugs.ruby-lang.org/issues/14490#change-70417 * Author: sam.saffron (Sam Saffron) * Status: Open * Priority: Normal * Assignee: k0kubun (Takashi Kokubun) * Target version: * ruby -v: * Backport: 2.3: UNKNOWN, 2.4: UNKNOWN, 2.5: UNKNOWN ---------------------------------------- This was reported earlier but I would like to add some test methodology here: (tested using Discourse) ### What I tested 1. Run `ruby script/bench.rb` to warm up profiling database 2. Run `RUBYOPT='--jit --jit-verbose=1 --jit-max-cache=10000' RAILS_ENV=profile bin/puma -e production` 1. Increasing the cache size is an attempt to get higher hit rates 3. WAIT 5-15 or so minutes for all jitting to stop so we have no cross talk 4. Run `ab -n 100 http://localhost:9292/` 5. Wait for all new jitting to finish 6. Run `ab -n 100 http://localhost:9292/` The absolute best I get is around **61ms** median for the test. With MJIT This is MJIT results! ``` Percentage of the requests served within a certain time (ms) 50% 61 66% 63 75% 70 80% 71 90% 73 95% 83 98% 106 99% 109 100% 109 (longest request) ``` Compared to w/o MJIT which is: ``` Percentage of the requests served within a certain time (ms) 50% 47 66% 48 75% 50 80% 51 90% 60 95% 62 98% 75 99% 77 100% 77 (longest request) ``` ### Theory on why this happens I suspect this is happening cause we are introducing new overhead to every single method dispatch (counting for mjit, and hash lookup and so on). This overhead adds up. -- https://bugs.ruby-lang.org/ Unsubscribe: <mailto:[email protected]?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>