Gregory's Server
Profiling Deno with Chrome DevTools
This is a period of about 8 seconds. A long-running function is destroying performance. Width is the important axis here, and that huge block in the middle goes very wide. When that happens, one CPU core spikes to 100%. (The other CPU cores will not be used automatically, because Deno processes are tied to a specific thread)
I can zoom in to see the stack at this time. It's `trendingTagsController`. That makes sense, because it's very unoptimized. I know this. As a quick fix, I will cache it, and then consider moving it to a Web Worker.
This is a period of about 8 seconds. A long-running function is destroying performance. Width is the important axis here, and that huge block in the middle goes very wide. When that happens, one CPU core spikes to 100%. (The other CPU cores will not be used automatically, because Deno processes are tied to a specific thread)
I can zoom in to see the stack at this time. It's `trendingTagsController`. That makes sense, because it's very unoptimized. I know this. As a quick fix, I will cache it, and then consider moving it to a Web Worker.