Similarly, we collected the results on a system with 4-core i3(TM) processor, 4GB RAM, 1TB 5,400rpm mechanical hard disk, and Intel(R) HD 440 graphics, on Fedora 29 Workstation and Kubuntu 18.10 distributions. The results below were gathered on a system with 6-core/12-thread Xeon(TM) processor, 64GB RAM, 2TB 970 EVO NVMe SSD, and Nvidia Quadro(R) P2000 GPU. We conducted several permutations of this test, including different hardware platforms, Linux distributions, and packaging formats (DEB, RPM and Snaps). After the installation, we timed the loading of Vscode. We tested the behavior of the Vscode application,as it’s a fairly representative example of a GUI-based software. We simulated a typical run of an application after it’s been installed, the same way a Linux user would do. We took this problem seriously, and implemented changes that resolve most of the issues, and we’d like to talk about them here. In general, with graphical software, this used to take a fair deal of time, causing a delay in application opening, and would impair the user experience. The one aspect of the application usage sequence we did not cover in that piece was the first-time run just after the installation. We tested GIMP and VLC on both Ubuntu and Fedora, with some rather interesting findings.
Several months ago, we shared an article titled I have a need, a need for snap that detailed the application performance results of snaps compared to their classic repo counterparts.
0 kommentar(er)
