When I first read fork-join, I was thinking of the syscalls fork and wait. Is there any scenario that could benefit from the the much more heavyweight operation of spawning a copy of the current process and waiting for it's children to finish as opposed to spawning threads?
metainf
@kapalani From what I've read, the reason why processes are used over threads is that even though making new processes is a fairly expensive operation, its easier to not run into shared memory issues that threading can have.
When I first read fork-join, I was thinking of the syscalls fork and wait. Is there any scenario that could benefit from the the much more heavyweight operation of spawning a copy of the current process and waiting for it's children to finish as opposed to spawning threads?
@kapalani From what I've read, the reason why processes are used over threads is that even though making new processes is a fairly expensive operation, its easier to not run into shared memory issues that threading can have.