[#60404] is RB_GC_GUARD needed in rb_io_syswrite? — Eric Wong <normalperson@...>
I haven't gotten it to crash as-is, but it seems like we need to
4 messages
2014/02/01
[#60682] volatile usages — Eric Wong <normalperson@...>
Hi all, I went ahead and removed some use of volatile which were once
5 messages
2014/02/13
[#60794] [RFC] rearrange+pack vtm and time_object structs — Eric Wong <normalperson@...>
Extracted from addendum on top of Feature #9362 (cache-aligned objects).
4 messages
2014/02/16
[#61139] [ruby-trunk - Feature #9577] [Open] [PATCH] benchmark/driver.rb: align columns in text output — normalperson@...
Issue #9577 has been reported by Eric Wong.
3 messages
2014/02/28
[ruby-core:61068] Re: [ruby-trunk - Bug #9518] Objects in large arrays are leaked
From:
Eric Wong <normalperson@...>
Date:
2014-02-25 10:06:14 UTC
List:
ruby-core #61068
The yahns HTTP server uses a long-lived fdmap array to map Fixnum(fileno) -> IO connections. This array exists prevent GC from sweeping IOs (because IOs are watched by Linux epoll and not markable w/o an Array to store them). 64K+ connections (array size) is attainable with yahns. The long-lived fdmap array lifetime should not infect the short lived client connections. If I were to allow >=64K client connections on my public yahns instance, clients will cause memory leaks/waste. (yahns supports infinitely-lived connections, but in practice, clients connections tend to be short-lived).