Re:How a fix in Go 1.9 sped up our Gitaly service by 30x
by arghwhat on Monday January 29, 2018 @04:29AM
(#16256415)
Definitely. While fork(2) is expensive, a price is useless without also knowing the budget, and how expensive it is depends on the environment.
However, the problem in the posted article was indeed that spawning Git processes 20 times a second in that specific Go application was too much, and the fix was that Go replaced fork(2) with posix_spawn(3).
> What's really wrong here is that they're apparently spawning processes like crazy.
Sounds like it depends on the use-case, rather then blanket "two dozen processes per second is clearly absurd".