|
|
|
|
|
|
by tom_mellior
1851 days ago
|
|
|
> Here's the summary: [...] But running multi-process is heavy on the JVM as it has to load the virtual machine and JIT for every process start, special when the processes are short lived. This is a valid summary of some facts, but not of the article or facts relevant to the article. Some quotes: "Jekyll is not forking processes, so that is not the issue." "The area where JRuby and TruffleRuby shine are long running processes that have had time to warm up. Based on suggestions I put together a repo of a simple small Jekyll build being built 20 times by the same process in a repo here. After 20 builds with the same running process the build times do start to converge, but even after that MRI Ruby is still fastest." |
|
|