Editor Performance test: Atom, VS Code, Sublime text_ Editor

When it comes to text editors, I've been using Sublime text for almost three years and haven't had any problems. A couple of years ago, I tried to use Atom, its active community (GITHUB). I love GitHub) left me with a deep impression. Atom's UI design is particularly appealing to me, but I still insist on using Sublime Text because of performance problems: Even after the Atom 1.0 release, Atom is still too slow.

These days, I searched Google for "Sublime Text vs Atom 2016" and wanted to see if Atom had any significant improvement. Then I saw Visual Studio Code. vs code, like Atom, was created using WEB technology, but critics say vs code is faster. So I want to do a little test to see the difference in performance of these kinds of editors. Editor versions Editor version Sublime Text 3 beta, build 3126 Atom 1.12.7 Visual Studio Code 1.8.1 textedit 1.12 (329) method

For testing hardware: MacBook Pro 2016 13-inch with Touch Bar, (2.9 GHz Intel Core i5 CPU, 8GB 2133 MHz LPDDR3 RAM, running MacOS Sierra). All visible programs are turned off. Use MacOS's own textedit as a reference. Launch time to start

Each type of editor is started from the Dock by clicking on the icon. I recorded the length of the process from the click of the icon to the full load of the first window. Window open Time window is opened

Start each type of editor first, then close all windows. I recorded the length of time when the first window was fully loaded from the Dock menu (or other equivalent menu) by clicking "New Window". Files open time when the file was opened

Start each editor first and open a window. Drag a file from the Finder to the Editor's window. I recorded the length of time from the release of the file to the full load of the file. Files Generating file generation

Use the following Python script to generate four files containing 10,000 lines, 1 million lines, 1 million lines, and 10 million lines of text, respectively, 370KB, 3.7MB, 37MB, and 370MB.   Python 1 2 3 4 5 6 7 8 (9) template = ' ' #include <iostream>-----   int main () {return 0;} /*%s/' string = ' abcdefghijklmnopqrstuvwxyz1234567890n ' with open (' Test-10k.cpp ', ' W ') as f:f. Write (template% (String * 10000,)) with open (' Test-100k.cpp ', ' W ') as f:f. Write (template% (String * 100000,)) with open (' Test-1m.cpp ', ' W ') as f:f. Write (template% (String * 1000000,)) with open (' Test-10m.cpp ', ' W ') as f:f. Write (template% (String * 10000000,))

Files open time file opened

First, open each editor and load a file. I use Activity Monitor to add up all the memory consumed by the process. The file used in this procedure is the file size 370KB in the file open time test. Result start time (in seconds)

Note: TextEdit does not open the edit window at startup, but instead opens a window that selects the file. Window open time (in seconds)

Note: TextEdit Open the window when there is a pop-up animation, which will slow down a little time file open time (in seconds)

Note: Atom cannot open "1 million lines" file and will report "Crash" in about 40 seconds. Visual Studio Code does not allow me to open "10 million rows" of files, will report "too large" Atom in the Open "100,000 rows" of the file can not maintain syntax highlighting. Visual Studio code cannot keep syntax highlighting when you open a 1 million-line file. TextEdit does not have a syntax highlighting feature. TextEdit has a pop-up animation when the file is opened, slowing down a little bit. Memory usage (in MB)

Conclusion

The performance of Atom and VS Code is significantly worse than Sublime Text and TextEdit: The time to start and open a window is obviously slow for a few seconds and consumes more memory.

In terms of opening files and using RAM, Visual Studio Code is better than atom, which can handle larger files and faster than atom. When I test this file for 3.7MB, Visual Studio Code can open in a second, but Atom takes more than two seconds.

Sublime Text is still the king of Speed, Visual Studio Code Second, Atom Countdown first.

Digression: Starting this month, I'm going to use Visual Studio code instead of Sublime text, and Visual Studio code looks better.

This article by Bole Online-Liu Sing translation, Huang Li-min school manuscript

from:http://blog.jobbole.com/109756/