<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none"><!-- p { margin-top: 0px; margin-bottom: 0px; }--></style>
</head>
<body dir="ltr" style="font-size:12pt;color:#000000;background-color:#FFFFFF;font-family:Calibri,Arial,Helvetica,sans-serif;">
<p><span style="font-size: 12pt; color: rgb(33, 33, 33);">> I wonder if we can see that much difference on SSDs.</span></p>
<p><span style="font-size: 12pt; color: rgb(33, 33, 33);"><br>
</span></p>
<p>Do not know anything about SSD yet, but this technique was a sub-part of optimization for<br>
</p>
<p>FireFox on android (https://glandium.org/blog/?p=2467). </p>
<p>And they shared some numbers which looks nice:<br>
</p>
<p><br>
</p>
<p><a href="https://docs.google.com/spreadsheets/d/1MqO4rGgKw8B6OVWlS1QHoquLUWSExybcN_jEVTHcpV8/edit#gid=1">https://docs.google.com/spreadsheets/d/1MqO4rGgKw8B6OVWlS1QHoquLUWSExybcN_jEVTHcpV8/edit#gid=1</a><br>
</p>
<p><br>
</p>
<p>Note that number is a result non only of section ordering, they use faulty.lib which is custom dynamic loader,<br>
</p>
<p>and compress chunks of libraries. Section ordering allows them group hot sections and <span style="font-size: 12pt;">decompress less chunks on startup then.</span><span style="font-size: 12pt;"></span></p>
<p><br>
</p>
<p>George.<br>
</p>
</body>
</html>