Difference between revisions of "Performance/Reorder Symbols For Libraries"
From Apache OpenOffice Wiki
(→Reorder symbols for libraries to improve file I/O) |
(→Reorder symbols for libraries to improve file I/O) |
||
| Line 1: | Line 1: | ||
| − | = Reorder | + | = Reorder code/data for libraries to improve file I/O = |
| − | The [http://wiki.services.openoffice.org/wiki/Performance/OOo31_LibrariesOnStartup#Cold_startup_Writer_.28without_AV_real-time_protection.29 comprehensive analysis] of the cold start up behavior of OpenOffice.org shows that file I/O is main bottleneck. About 80% of the start up time is spent waiting for data from the disk. Most file I/O depends on library loading. This part describes what can be done to reduce I/O time for loading OpenOffice.org libraries. The main ideas are system independent but the solutions must be system/compiler specific. The following chapters in detail how we want to | + | The [http://wiki.services.openoffice.org/wiki/Performance/OOo31_LibrariesOnStartup#Cold_startup_Writer_.28without_AV_real-time_protection.29 comprehensive analysis] of the cold start up behavior of OpenOffice.org shows that file I/O is main bottleneck. About 80% of the start up time is spent waiting for data from the disk. Most file I/O depends on library loading. This part describes what can be done to reduce I/O time for loading OpenOffice.org libraries. The main ideas are system independent but the solutions must be system/compiler specific. The following chapters describe in detail how we want to reorder code/data within the libraries. |
== Windows == | == Windows == | ||
| + | |||
| + | This chapter describes the solution for the Windows platform. | ||
== Microsoft Visual Studio 2008 C/C++ compiler== | == Microsoft Visual Studio 2008 C/C++ compiler== | ||
Revision as of 20:49, 21 March 2009
Reorder code/data for libraries to improve file I/O
The comprehensive analysis of the cold start up behavior of OpenOffice.org shows that file I/O is main bottleneck. About 80% of the start up time is spent waiting for data from the disk. Most file I/O depends on library loading. This part describes what can be done to reduce I/O time for loading OpenOffice.org libraries. The main ideas are system independent but the solutions must be system/compiler specific. The following chapters describe in detail how we want to reorder code/data within the libraries.
Windows
This chapter describes the solution for the Windows platform.
