The project I'm working on right now (Rails) could certainly use the hell out of it. Hell, people were thrilled by how much faster things were after I pushed everything that didn't need to happen at request-time into the background queue.
Just having futures to keep database access would help, although I'm not sure how that would be possible with Rails' lazy querying.
All that said, the core Ruby guys are probably better off spending their time on performance enhancements than removing enough of the GIL to allow that kind of multithreaded shenanigans.
Just having futures to keep database access would help, although I'm not sure how that would be possible with Rails' lazy querying.
All that said, the core Ruby guys are probably better off spending their time on performance enhancements than removing enough of the GIL to allow that kind of multithreaded shenanigans.