[#64210] Asking for clarification for exception handling usage — Rodrigo Rosenfeld Rosas <rr.rosas@...>
I've created a ticket for that but didn't get any feedback so I decided
[#64517] Fw: Re: Ruby and Rails to become Apache Incubator Project — Tetsuya Kitahata <kitahata@99.alumni.u-tokyo.ac.jp>
What do you think? >> Ruby developers
What benefits are there to this? I have a feeling that adding unnecessary
On Sat, 23 Aug 2014 22:43:46 -0700
Here I am a Japanese. Before moving anywhere else answer to our question first: what benefits?
tax issue with each other.
Forgot to assert my opinions:
[#64614] cowspace (work-in-progress) — Eric Wong <normalperson@...>
Hi all, I started working on a cowspace branch. Based on the mspace API
[#64615] [ruby-trunk - Feature #10181] [Open] New method File.openat() — oss-ruby-lang@...
Issue #10181 has been reported by Technorama Ltd..
I like this feature.
On 08/28/2014 02:53 PM, Eric Wong wrote:
Joel VanderWerf <joelvanderwerf@gmail.com> wrote:
On 08/29/2014 12:55 AM, Eric Wong wrote:
Joel VanderWerf <joelvanderwerf@gmail.com> wrote:
[#64627] [ruby-trunk - Feature #10182] [PATCH] string.c: move frozen_strings table to rb_vm_t — ko1@...
Issue #10182 has been updated by Koichi Sasada.
[#64671] Fwd: [ruby-changes:35240] normal:r47322 (trunk): symbol.c (rb_sym2id): do not return garbage object — SASADA Koichi <ko1@...>
Why this fix solve your problem?
(2014/08/30 8:50), SASADA Koichi wrote:
SASADA Koichi <ko1@atdot.net> wrote:
Eric Wong <normalperson@yhbt.net> wrote:
(2014/08/31 0:18), Eric Wong wrote:
[ruby-core:64415] Re: [ruby-trunk - Bug #10009] IO operation is 10x slower in multi-thread environment
normalperson@yhbt.net wrote: > I doubt I can noticeably improve performance with futexes vs mutex/condvar. Totally not-speed-optimized futex-based lock/condvar implementation at git://bogomips.org/ruby.git (futex branch) http://bogomips.org/ruby.git/patch?id=ae93c50c8de I am not sure if my implementation is correct, but "make check" passes with both 8 cores and 1 core active (8-core Vishera). I will probably write an independent (C-only) test for more parallelism and maybe steal some from glibc (I also plan on using this futex-based lock implementation outside of Ruby). Benchmarks don't seem to show much (if any) improvement, yet. Speed improvement from reimplementing GVL around bare futex interface may be possible (w/o using separate condvar/mutex layer). On amd64 GNU/Linux, pthread_mutex_t is 40 bytes, but these futex-based locks only need 4 bytes. Similarly, pthread_cond_t is 48 bytes, making rb_nativethread_cond_t 56 bytes with pthreads; this futex implementation currently requires only 16 bytes for a condvar. Size improvement may be noticeable for some apps with many Mutexes: the lock/cond reductions mean rb_mutex_struct is now 48 bytes instead of 128 bytes.