Method used to measure the performance:-
We used iPhone 5S to capture the slo-mo (slow-motion) videos with 120 fps. After capturing the videos, we used Adobe Premier-Pro to calculate the time elapsed to the nearest frames for each of the events being considered(accuracy= 1/120th of a second).
Parameters to consider for testing this.
Project size used for the comparison - small (265 files, jquery project), medium (5602 files, brackets full src) and large (25852files, brackets src + many extensions) projects.
An iPhone 5S was used to capture slow-motion videos at 120 fps. After capturing the videos, we used Adobe Premiere-Pro to calculate the time elapsed to the nearest frames for each of the events being considered (accuracy= 1/120th of a second).
The testing configuration for all the apps where the default installer feature set for each of the latest versions of the apps as on 5th may 2015.
File open times
For this test, the time to open a single file from a project of the corresponding size was measured averaged over 3 events. For brackets, sublime and VS code, this would mean a double click(start of first click) on a file in the project tree and all events including syntax highlighting complete and the UI render complete. For atom, as single click always opens a file in a tab, the same was the file open criteria.
Sublime seems to have higher file open times due to our 'definition' of file open time as all UI render complete. As sublime has an animation on new tabs coming up and this slows down the times; but sublime always rendered the text area swiftly.
debug > Show performance data
File switch times
For this test, the time to switch to a single file from a project of the corresponding size was measured averaged over 3 events. This event means a single click on any of the files in the file tree as the starting point and all UI rendered including the syntax coloring as the end point.
@abose did we test this before or after this fix landed? #11043
Or did we just test 1.3?
It was tested on shipping builds (1.3 with extract). The dev builds are usually significantly(in 100xmilli secs) slower as observed while measuring, so I stuck with the release builds.
After profiling file open times, three major areas of optimization candidates are
+1 for a fix for mac.
I almost switched to a different editor the other day because of how long it takes.. I'm sure I'm not the only one too.
+1 for a fix for mac. Switched to Sublime :(
+1 for a fix for a mac. Still crazy slow, again tempting to swap to sublime
I ended up switching to sublime, best choice I ever made.
+1 for macs. It's definitely slowed down for me too.