Starting a tmux session in conjunction with several compilation intensive yarn start ... commands causes those node processes to take up significant amounts of CPU. This seems to happen only when using the .tmux.conf provided by https://github.com/gpakosz/.tmux (not yet 100%).
Starting a
tmux
session in conjunction with several compilation intensiveyarn start ...
commands causes thosenode
processes to take up significant amounts of CPU. This seems to happen only when using the.tmux.conf
provided by https://github.com/gpakosz/.tmux (not yet 100%).Possibly related issue - https://github.com/gpakosz/.tmux/issues/247 (check out
optimizations
branch).