[#45906] ' failures. — Tanaka Akira <akr@...>
' の扱いが変化したことで、テストが失敗しているようです。
9 messages
2012/07/04
[#45910] [ruby-trunk - Bug #6694][Open] Thread.new without block. — "ko1 (Koichi Sasada)" <redmine@...>
24 messages
2012/07/04
[#45928] Re: [ruby-cvs:43524] kosaki:r36348 (trunk): * include/ruby/ruby.h: Removed RUBY_GLOBAL_SETUP complely. It is — SASADA Koichi <ko1@...>
ささだです．
3 messages
2012/07/09
[#45973] [ruby-trunk - Bug #6751][Assigned] remove tempfiles early. — "akr (Akira Tanaka)" <akr@...>
4 messages
2012/07/18
[#45976] [ruby-trunk - Bug #6756][Open] FileUtils.rm_rf がアクセス権のない空ディレクトリを削除しない — "fumiyas (Fumiyasu SATOH)" <fumiyas@...>
9 messages
2012/07/20
[#45977] [ruby-trunk - Feature #6757][Open] [PATCH] Add Process.getsid — "fumiyas (Fumiyasu SATOH)" <fumiyas@...>
6 messages
2012/07/20
[#46012] [ruby-trunk - Feature #6812][Open] Refactor gc.c — "authorNari (Narihiro Nakamura)" <authorNari@...>
13 messages
2012/07/30
[ruby-dev:45989] Re: [ruby-trunk - Feature #6694] Thread.new without block.
From:
KOSAKI Motohiro <kosaki.motohiro@...>
Date:
2012-07-21 05:53:15 UTC
List:
ruby-dev #45989
> I don't think I understand your question. To summarize my objection to this proposed API change: Thread stack size should be something set at the VM level completely outside of Ruby code. Ruby code should not be coupled with implementation details. If I understand correctly, you suggested Thread and Fiber should have enough large stack size. I 100% agree. Then almost all ruby programmers don't need bother stack size issue. The problem is, *current* fiber implementation have merely very small stack size and it often caused stack overflow issue. Why it is so small? Because of, larger stack size restricted maximum number of fibers. Think, stack-size * number-of-fibers should be < 3G if system is running on 32bit OS. So, we hope to increase stack size for just your opinion. but it has one down size. it reduce a number of maximum fibers. The next question is, anybody need such so many thread/fibers? Is this real issue? Unfortunately, we can't answer it. It depend on ruby scripts. Out of ruby world, I know some game programmer prefer to create a lot of fibers. But I don't know real ruby use case. However, I hope to keep *a way* to create a lot of fibers if programmer don't hesitate deep system/cpu depending scripts. Finally, if you agree fiber issue and you think only fiber should have stack size parameter, can you please explain why do you dislike thread and fiber have the same interface? Usually, thread and fiber should keep same or similar interface because it reduce learning cost. Thank you.
