Describe the bug
Running this demo (using npm run demo) - causes the fan on my laptop (2018 mbp, MacOS 10.13.6) to go wild – in activity monitor, node gets up to 250% CPU, 13 threads... I luckily don't have this problem after testing out a compiled distribution demo with just a python/LAMP webserver. I'm guessing the issue is due to either concurrently, rollup, or live-server? Great that it recompiles and refreshes, but I'm not sure it's worth it for the stress and fan noise. Is this normal behavior for a live-changes setup? How would I best reduce this and simply compile on demand, as I have no problem refreshing the browser window if that's potentially causing it. Not familiar enough with node and packing js to know where to look/disable.
Thanks for any tips to calm my fans.
To Reproduce
Steps to reproduce the behavior:
npm run demo
Wait 5 sec for fans to go into overdrive
Check Activity Monitor
See node with 150 – 250% CPU
Expected behavior
Fans to be calm, maybe whirl up for a second while recompiling?
Environment Information
Latest chrome / node v15.4.0 / npm v7.0.15
yjs v13.0.0
Additional context
PS – getting very close to building an ace-editor demo for yjs..! Will share once I solve cursors/selections syncing.
Describe the bug Running this demo (using
npm run demo) - causes the fan on my laptop (2018 mbp, MacOS 10.13.6) to go wild – in activity monitor,nodegets up to 250% CPU, 13 threads... I luckily don't have this problem after testing out a compiled distribution demo with just a python/LAMP webserver. I'm guessing the issue is due to eitherconcurrently,rollup, orlive-server? Great that it recompiles and refreshes, but I'm not sure it's worth it for the stress and fan noise. Is this normal behavior for a live-changes setup? How would I best reduce this and simply compile on demand, as I have no problem refreshing the browser window if that's potentially causing it. Not familiar enough with node and packing js to know where to look/disable.Thanks for any tips to calm my fans.
To Reproduce Steps to reproduce the behavior:
npm run demonodewith 150 – 250% CPUExpected behavior Fans to be calm, maybe whirl up for a second while recompiling?
Environment Information
Additional context PS – getting very close to building an ace-editor demo for yjs..! Will share once I solve cursors/selections syncing.