I'm in the office hard at work trying to avoid working on the project I'm supposed to work on by working furiously on one of my other projects. This is normal.
-
Show this thread
-
Well, I have what seems to be a working replacement for std::rc::Rc with transparent memory pooling, which should make http://immutable.rs quite a bit faster overall, and I'm just going to leave it there and write the tests in the morning so I can feel good about it tonight.
2 replies 1 retweet 23 likesShow this thread -
I've attempted this several times before, and it always comes to grief, either through the borrow checker or through extremely undefined behaviour. But maybe this time I got it right.
2 replies 0 retweets 12 likesShow this thread -
Don't tell anyone, but I may have been working since I got home until nearly 2am on this problem. Especially don't tell me, I'll be disappointed af in myself if I ever find out.
2 replies 1 retweet 23 likesShow this thread -
I could have been catching Pokémon.
2 replies 0 retweets 11 likesShow this thread -
OK, well, it's not the massive performance boost I'd been hoping for, but at least it's visible. Might actually shave 1% off the http://immutable.rs benchmarks with some luck.pic.twitter.com/ktpj6p8sLJ
1 reply 0 retweets 8 likesShow this thread -
The moral of the story is: don't underestimate the system allocator, it's not actually as slow as they want you to believe.
3 replies 0 retweets 16 likesShow this thread -
Replying to @bodil
I'd be interested to see the same numbers with the jemallocator crate used. I was talking with
@yoshuawuyts about this recently, and jemallocator closed the gap between system allocator and a local pool2 replies 0 retweets 1 like
Tilting point for us was about 6kb allocations; which is just about the number you want for buffered network reads/writes. But yeah, impressed at how good the allocator is!
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.