[#44036] [ruby-trunk - Feature #6242][Open] Ruby should support lists — "shugo (Shugo Maeda)" <redmine@...>
20 messages
2012/04/01
[#44084] [ruby-trunk - Bug #6246][Open] 1.9.3-p125 intermittent segfault — "jshow (Jodi Showers)" <jodi@...>
22 messages
2012/04/02
[#44156] [ruby-trunk - Feature #6265][Open] Remove 'useless' 'concatenation' syntax — "rosenfeld (Rodrigo Rosenfeld Rosas)" <rr.rosas@...>
45 messages
2012/04/06
[#44207] [ruby-trunk - Feature #6265] Remove 'useless' 'concatenation' syntax
— "mame (Yusuke Endoh)" <mame@...>
2012/04/09
[#44211] Re: [ruby-trunk - Feature #6265] Remove 'useless' 'concatenation' syntax
— Yukihiro Matsumoto <matz@...>
2012/04/09
Hi,
[#44232] Re: [ruby-trunk - Feature #6265] Remove 'useless' 'concatenation' syntax
— SASADA Koichi <ko1@...>
2012/04/09
(2012/04/09 14:19), Yukihiro Matsumoto wrote:
[#44163] [ruby-trunk - Bug #6266][Open] encoding related exception with recent integrated psych — "jonforums (Jon Forums)" <redmine@...>
10 messages
2012/04/06
[#44233] [ruby-trunk - Bug #6274][Open] Float addition incorrect — "swanboy (Michael Swan)" <swanyboy4@...>
3 messages
2012/04/09
[#44303] [ruby-trunk - Feature #6284][Open] Add composition for procs — "pabloh (Pablo Herrero)" <pablodherrero@...>
57 messages
2012/04/12
[#44329] [ruby-trunk - Feature #6287][Open] nested method should only be visible by nesting/enclosing method — "botp (bot pena)" <botpena@...>
4 messages
2012/04/13
[#44349] [ruby-trunk - Feature #6293][Open] new queue / blocking queues — "tenderlovemaking (Aaron Patterson)" <aaron@...>
10 messages
2012/04/13
[#44354] [ruby-trunk - Feature #6293][Assigned] new queue / blocking queues
— "mame (Yusuke Endoh)" <mame@...>
2012/04/14
[#44357] Re: [ruby-trunk - Feature #6293][Assigned] new queue / blocking queues
— Aaron Patterson <tenderlove@...>
2012/04/14
On Sat, Apr 14, 2012 at 10:58:12AM +0900, mame (Yusuke Endoh) wrote:
[#44384] Re: [ruby-trunk - Feature #6293][Assigned] new queue / blocking queues
— SASADA Koichi <ko1@...>
2012/04/16
Hi,
[#44391] Re: [ruby-trunk - Feature #6293][Assigned] new queue / blocking queues
— Aaron Patterson <tenderlove@...>
2012/04/16
On Mon, Apr 16, 2012 at 06:25:59PM +0900, SASADA Koichi wrote:
[#44372] Possible merge error of code in Issue 4651 on to Ruby 1.9.3-p125? — "Blythe,Aaron" <ABLYTHE@...>
tl;dr I believe I have uncovered a merge error to ruby 1.9.3-p125 from Issu=
3 messages
2012/04/16
[#44431] [Backport93 - Backport #6314][Open] Backport r35374 and r35375 — "drbrain (Eric Hodel)" <drbrain@...7.net>
4 messages
2012/04/18
[#44432] [ruby-trunk - Feature #6315][Open] handler to trace output of each line of code executed — "ankopainting (Anko Painting)" <anko.com+ruby@...>
9 messages
2012/04/18
[#44533] [ruby-trunk - Bug #6341][Open] SIGSEGV: Thread.new { fork { GC.start } }.join — "rudolf (r stu3)" <redmine@...>
24 messages
2012/04/22
[#44564] [ruby-trunk - Bug #6341] SIGSEGV: Thread.new { fork { GC.start } }.join
— "kosaki (Motohiro KOSAKI)" <kosaki.motohiro@...>
2012/04/23
[#44573] Re: [ruby-trunk - Bug #6341] SIGSEGV: Thread.new { fork { GC.start } }.join
— Yusuke Endoh <mame@...>
2012/04/24
Hello,
[#44577] Re: [ruby-trunk - Bug #6341] SIGSEGV: Thread.new { fork { GC.start } }.join
— KOSAKI Motohiro <kosaki.motohiro@...>
2012/04/24
On Mon, Apr 23, 2012 at 11:17 PM, Yusuke Endoh <mame@tsg.ne.jp> wrote:
[#44582] Re: [ruby-trunk - Bug #6341] SIGSEGV: Thread.new { fork { GC.start } }.join
— Yusuke Endoh <mame@...>
2012/04/24
Hello,
[#44596] Re: [ruby-trunk - Bug #6341] SIGSEGV: Thread.new { fork { GC.start } }.join
— KOSAKI Motohiro <kosaki.motohiro@...>
2012/04/24
(4/24/12 6:55 AM), Yusuke Endoh wrote:
[#44579] [ruby-trunk - Bug #6341] SIGSEGV: Thread.new { fork { GC.start } }.join
— "naruse (Yui NARUSE)" <naruse@...>
2012/04/24
[#44581] Re: [ruby-trunk - Bug #6341] SIGSEGV: Thread.new { fork { GC.start } }.join
— KOSAKI Motohiro <kosaki.motohiro@...>
2012/04/24
> kosaki (Motohiro KOSAKI) wrote:
[#44540] [ruby-trunk - Bug #6343][Open] Improved Fiber documentation — "andhapp (Anuj Dutta)" <anuj@...>
6 messages
2012/04/23
[#44612] [ruby-trunk - Feature #6354][Open] Remove escape (break/return/redo/next support) from class/module scope — "ko1 (Koichi Sasada)" <redmine@...>
8 messages
2012/04/25
[#44630] [ruby-trunk - Feature #6361][Open] Bitwise string operations — "MartinBosslet (Martin Bosslet)" <Martin.Bosslet@...>
31 messages
2012/04/26
[#44713] [ruby-trunk - Feature #6361] Bitwise string operations
— "MartinBosslet (Martin Bosslet)" <Martin.Bosslet@...>
2012/04/28
[#44731] Re: [ruby-trunk - Feature #6361] Bitwise string operations
— KOSAKI Motohiro <kosaki.motohiro@...>
2012/04/28
On Fri, Apr 27, 2012 at 8:53 PM, MartinBosslet (Martin Bosslet)
[#44759] Re: [ruby-trunk - Feature #6361] Bitwise string operations
— Joshua Ballanco <jballanc@...>
2012/04/29
On Saturday, April 28, 2012 at 8:52 AM, KOSAKI Motohiro wrote:
[#44636] [ruby-trunk - Bug #6364][Open] Segmentation fault happend when running test_cptr.rb — "raylinn@... (ray linn)" <raylinn@...>
9 messages
2012/04/26
[#44667] possible YAML bug in ruby 1.9.3p125? — Young Hyun <youngh@...>
YAML in ruby 1.9.3p125 seems to have a bug reading in YAML from older =
4 messages
2012/04/27
[#44686] [BUG] not a node 0x07 — ronald braswell <rpbraswell@...>
Running ruby 1.8.6 on Solaris 10.
7 messages
2012/04/27
[#44688] Re: [BUG] not a node 0x07
— "NARUSE, Yui" <naruse@...>
2012/04/27
2012/4/28 ronald braswell <rpbraswell@gmail.com>:
[#44694] Re: [BUG] not a node 0x07
— ronald braswell <rpbraswell@...>
2012/04/27
I have heard reports of this on 1.9.x. Do you know if this problem has
[#44704] [ruby-trunk - Feature #6373][Open] public #self — "trans (Thomas Sawyer)" <transfire@...>
61 messages
2012/04/27
[#44735] [ruby-trunk - Feature #6373] public #self
— "matz (Yukihiro Matsumoto)" <matz@...>
2012/04/28
[#59892] [ruby-trunk - Feature #6373] public #self
— ruby-core@...
2014/01/20
Issue #6373 has been updated by Marc-Andre Lafortune.
[#44743] [ruby-trunk - Feature #6375][Open] Python notation for literal Hash — "alexeymuranov (Alexey Muranov)" <redmine@...>
10 messages
2012/04/28
[#44748] [ruby-trunk - Feature #6376][Open] Feature lookup and checking if feature is loaded — "trans (Thomas Sawyer)" <transfire@...>
13 messages
2012/04/28
[#44832] [ruby-trunk - Feature #6376][Feedback] Feature lookup and checking if feature is loaded
— "mame (Yusuke Endoh)" <mame@...>
2012/05/03
[#44835] Re: [ruby-trunk - Feature #6376][Feedback] Feature lookup and checking if feature is loaded
— Nikolai Weibull <now@...>
2012/05/03
On Thu, May 3, 2012 at 6:02 AM, mame (Yusuke Endoh) <mame@tsg.ne.jp> wrote:
[ruby-core:44186] [ruby-trunk - Bug #6183] Enumerator::Lazy performance issue
From:
"gregolsen (Innokenty Mikhailov)" <anotheroneman@...>
Date:
2012-04-08 09:32:16 UTC
List:
ruby-core #44186
Issue #6183 has been updated by gregolsen (Innokenty Mikhailov).
File lazy_enumerator_hybrid.diff added
(Yusuke Endoh) wrote:
> (1..10).lazy.select {|x| false }.map {|x| p x }.to_a
> should print nothing, but it actually prints 1, 2, ..., 10
Fixed, thanks.
> But I guess implementing
> other methods, especially, #cycle and #zip, will make some
> functions (process_element and lazy_iterator_block) complex
> and hard to maintain.
Agree, those methods (especially #cycle) will be hard to implement in terms of procs chaining approach.
(Nobu Nakada) wrote:
> So I want to see this being merged in an extensible way.
I came up with a new hybrid patch.
It uses procs chaining to handle lazy #map and #select, and current enumerator chaining approach for other methods.
I believe this is an extensible way. We can move forward step by step and we can stop any time.
If those tricky #zip and #cycle methods optimization won't worth the code complexity added - we can leave it as it is: based on enumerator chaining.
See new lazy_enumerator_hybrid.diff (tests are green except test_inspect).
Please, let me know you thoughts about this.
----------------------------------------
Bug #6183: Enumerator::Lazy performance issue
https://bugs.ruby-lang.org/issues/6183#change-25714
Author: gregolsen (Innokenty Mikhailov)
Status: Assigned
Priority: Low
Assignee: nobu (Nobuyoshi Nakada)
Category:
Target version:
ruby -v: ruby 2.0.0dev (2012-03-17 trunk 35075) [x86_64-linux]
I benchmarked Enumerator::Lazy and that's what I got:
user system total real
Lazy: 0.690000 0.010000 0.700000 ( 0.733160)
Normal: 0.160000 0.010000 0.170000 ( 0.186695)
It seems like even with 4 chain links and 3000 elements in initial array, Lazy enumerator is almost 4(!) times slower than the normal case.
Instead of performance benefit we've got 4 times performance drawback.
See test file attached.
--
http://bugs.ruby-lang.org/