Re:Ruby Garbage Collection: Still Not Ready for Production
by yummyfajitas on Saturday March 29, 2014 @10:21PM
(#7494876)
Building a JVM is harder than building an RVM. I was asking from the perspective of user code. Shared memory requires mutexes in both threaded and forked code - this is not an advantage of multiple processes. In fact, multiprocess shared memory is generally harder to work with than threaded shared memory.
[ Parent
| on HN ]
Re:Ruby Garbage Collection: Still Not Ready for Production
by otterley on Monday March 31, 2014 @02:49PM
(#7503364)
We're talking about Ruby here, though. MRI threading has concurrency limitations, so processes are better here IMO.
I tend to think out of the box for multiprocess shared memory - Kyoto Cabinet and Redis can be helpful here, to name a few. Even SysV shared memory is pretty easy to use.