Ah, I have unstacked mails down to this one. Good reading, thanks Tim. Personnally, I like:
Another pattern uses fork to capture a consistent snapshot of a running process’s address space, allowing the parent to continue execution; this includes persistence support in Redis [68],
just because that's what I proposed a few years ago for our VM ;) And it probably was a good idea to reject this proposal, since fork is not a panacea as demonstrated in the article. The fact that an idea is shared does not make it good, I may say not completely stupid for own re-assurance ;)
Le sam. 14 déc. 2019 à 00:34, tim Rowledge tim@rowledge.org a écrit :
On 2019-11-29, at 5:28 AM, Ben Coman btc@openInWorld.com wrote:
Sharing an interesting paper I bumped into..
A fork() in the road
https://www.microsoft.com/en-us/research/uploads/prod/2019/04/fork-hotos19.p...
That's pretty interesting stuff. I never did understand the attraction of cloning an entire running process only to dump nearly all of it immediately. On the other hand, doing pretty much that (except we don't dump stuff) with an image seems to work really well...
tim
tim Rowledge; tim@rowledge.org; http://www.rowledge.org/tim Fractured Idiom:- PORTE-KOCHERE - Sacramental wine