General

Profile

ioquatix (Samuel Williams)

Issues

Activity

07/08/2018

11:35 AM Ruby trunk Bug #14900: Extra allocation in String#byteslice
I played around with my assumptions here. By far the worst from a memory POV was `slice!`, which given a string of 5M...
10:45 AM Ruby trunk Bug #14900: Extra allocation in String#byteslice
The way I've implemented it now (as in your first example) is something like this:
```
@buffer = read_data
if @b...
09:47 AM Ruby trunk Bug #14900: Extra allocation in String#byteslice
Yeah, I agree, this patch probably isn't right, but I just try to figure it out what is going on and suggest a soluti...
03:31 AM Ruby trunk Bug #14900: Extra allocation in String#byteslice
I think there are several things to consider here:
- Even though the string appears to be two allocations, it's on...
03:22 AM Ruby trunk Bug #14900: Extra allocation in String#byteslice
Okay I made an attempt to fix this: https://github.com/ruby/ruby/pull/1909
02:52 AM Ruby trunk Bug #14900: Extra allocation in String#byteslice
One thing I noticed if I freeze source string, the extra memory allocation goes away.
02:52 AM Ruby trunk Bug #14900: Extra allocation in String#byteslice
Okay, I reproduced the error. I made a test case here:
https://github.com/ioquatix/ruby/commit/9fb5cd644209efc7937...
02:02 AM Ruby trunk Feature #14736: Thread selector for flexible cooperative fiber based concurrency
I have updated the PR to use `transfer` in the scheduler, and I've added an example showing that it is composable wit...

07/07/2018

08:48 PM Ruby trunk Bug #14900: Extra allocation in String#byteslice
Nice catch I will try to verify on my end too

07/06/2018

09:16 AM Ruby trunk Feature #13618: [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid
> But we have example of Go: goroutine is a really green thread, and they do really scale.
Yes, they are great, bu...

Also available in: Atom