Below, are some numbers we have collected, but note, that this is still work in progress and this is just a snapshot data. It now seems to do a good job, optimizing the most important parts of the browser. We see improvements on a lot of different tasks, so we think we have trained the compiler well. In the startup tests Opera was stored on an SSD. The results below are from a computer running Windows 7 圆4, using an i7-6700 CPU locked at 3.4 GHz. It does not matter to a human, if a click is processed in 2 milliseconds or 1 millisecond, since humans are slow. The same for code related to user interaction. There is for instance code to handle errors, and rarely used web features, which does not have to be extremely fast, and can instead be made small and efficient. By selecting a number of important scenarios, the training set, we can teach the compiler, what code is important, and what is less important. With the help of Profile Guided Optimizations (PGO) we can do better. Unfortunately, it cannot try to make all the code fast, because that would make the program huge (and slow), so instead it tries to find a balance where programs become reasonably fast. Most of Opera is written in C++, and it is the C++ compiler’s job to convert the C++ to machine code, that a computer can run. If you like to check this build, just grab the installer. This is preview build for public testing. "We are working with making Opera even faster on Windows machines, using a technique named “PGO” (Profile Guided Optimizations”), and it’s time to show off the first results.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |