[#86787] [Ruby trunk Feature#14723] [WIP] sleepy GC — ko1@...

Issue #14723 has been updated by ko1 (Koichi Sasada).

13 messages 2018/05/01
[#86790] Re: [Ruby trunk Feature#14723] [WIP] sleepy GC — Eric Wong <normalperson@...> 2018/05/01

[email protected] wrote:

[#87095] [Ruby trunk Feature#14767] [PATCH] gc.c: use monotonic counters for objspace_malloc_increase — ko1@...

Issue #14767 has been updated by ko1 (Koichi Sasada).

9 messages 2018/05/17
[#87096] Re: [Ruby trunk Feature#14767] [PATCH] gc.c: use monotonic counters for objspace_malloc_increase — Eric Wong <normalperson@...> 2018/05/17

[email protected] wrote:

[ruby-core:86972] Re: [Ruby trunk Feature#13618] [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid

From: Eric Wong <normalperson@...>
Date: 2018-05-10 20:06:32 UTC
List: ruby-core #86972
[email protected] wrote:
> > Again, Mio (Glasgow Haskell Compiler) is most similar to what
> > I'm working on, here, and that scales to some ridiculous number
> > of cores
> 
> Thanks for that I will read it.

Fwiw, I've been citing Mio since before this feature was implemented...

> I will assume you've implemented something similar, but I have
> a question, when processing events, when handling events that
> don't belong to the current thread, you put them in a queue.
> How does the other thread know to wake up?

It enqueues an interrupt for the target thread, same thing as
"normal" thread switching.  Ruby uses a 100ms timeslice with
pthreads.

Unsubscribe: <mailto:[email protected]?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>

In This Thread

Prev Next