You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The file-watchers package dominates my CPU (99% CPU for any process that uses it). I tried both intensive-watch and robust-watch. I ran a quick profiling script and seems like 99.9% of the time is spent checking contracts. Using the defaults.
I may look into this further but thought I'd ping you now in case you have some tips.
Thanks for raising this. The contracts are not checking complicated structures, although one of them does consult the filesystem. I'm not sure if that would cause a CPU spike.
The profile actually alerted me to a loop that spins when it should be yielding time to other threads. I'll just need to rewrite some code to better leverage synchronizeable events.
Thanks for the easy to use lib @zyrolasting .
I'm a racket noob so go easy on me.
The file-watchers package dominates my CPU (99% CPU for any process that uses it). I tried both intensive-watch and robust-watch. I ran a quick profiling script and seems like 99.9% of the time is spent checking contracts. Using the defaults.
I may look into this further but thought I'd ping you now in case you have some tips.
outputs:
The text was updated successfully, but these errors were encountered: