Platform: Windows 10 (x86_64)
I quite often check log files, so tend to open files with several thousand lines of text. In order to see how Atom handles this case, I selected a few log files of various sizes, but didn’t get past the smallest file (710KB, 1000 lines) before hitting a snag.
Atom’s overall CPU usage (across various processes) goes up each time I open a log file. The ‘Runtime Broker’ process appears to ramp up at the same time, although to a slightly lesser degree, and during my tests CPU usage remained high until Atom was closed, at which point CPU levels dropped back to a quiet hum.
Side note, this is running 1.1.0 with no plugins or customization … I’m new in these parts and just trialling the editor for my purposes (not doing well so far, but I’d like it to).
I opened 5 sample log files, and found a constant 44% CPU usage of which about 30% was spread across various Atom processes. Most of the rest was taken up by the Runtime Broker process. I left this for just over a minute, and CPU usage remained fairly consistent. As soon as I closed Atom, Runtime Broker also stopped… I started up Atom again, all was quiet after an initial CPU spike … then I opened one log file. Atom goes up to 7% CPU usage, Runtime Broker’s up to 4%. I left this for roughly a minute, and noted no significant change during that time.