@headius @alex_gaynor @bascule but in what way is that statement you (re)tweeted true?
-
-
@bascule@envygeeks@voidspace Evidently not, though personally I'd prefer mutliple stackless processes to one running JVM. (personal pref) -
@rich0H@envygeeks@voidspace yeah, that's what I thought. I like shared heaps FOR SPEED! -
@bascule@envygeeks@voidspace I prefer IPC like sendfile(2) over shared heaps. That's personal though, not "this is better than that". -
@rich0H@envygeeks@voidspace there's a lot more complexity and inefficiency with that kind of approach, but it has some merits -
@bascule@envygeeks@voidspace inefficiency? MMU dependant I guess. scales across machines transpaently, but both valid. Case by case imo. -
@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 - 11 more replies
New conversation -
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.