@bascule troll EOF
@rich0H @envygeeks @voidspace having separate heaps per process and requiring context switches to copy data between procs is slow
-
-
@bascule@envygeeks@voidspace sendfile(2). Zero copy. If you're multicore there's no context switch. -
@rich0H@envygeeks@voidspace o_O I'm a big fan of sendfile but it's not really comparable to a lock-free data structure on a shared heap -
@bascule@envygeeks@voidspace I'm not saying "Shared heaps are bad". I'm saying they're not a magic bullet, and it's case by case. -
@rich0H@envygeeks@voidspace they're definitely more efficient. I'd challenge you to write something like Disruptor without one -
@bascule@envygeeks@voidspace So that's a case where they're more efficient? Which part of "case by case" was hard? -
@rich0H@envygeeks@voidspace IMO VMs that can't utilize multiple cores natively are not long for this world, at least for serious apps -
@bascule@envygeeks@voidspace Your assumption that all the cores live on the same box isn't a longterm worldview either! -
@rich0H@envygeeks@voidspace o_O umm here's one of my projects: https://github.com/celluloid/dcell - 5 more replies
New conversation -
-
-
@bascule@rich0H@voidspace sure, if it's 1992.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.