<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">[ Resent from correct account, so MacPorts won't bounce it back again ]<div><br><div><div>On Jan 2, 2008, at 12:22 PM, Tabitha McNerney wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Has anyone else noticed incredible MacPorts speed up improvements when installing various ports?<br><br>Here's an example: The same hardware (Xserve Intel 2 x 2 GhZ Dual Core Intel). Once this machine was running Tiger Server with MacPorts 1.5.0 and I installed the gcc41 port which (if my notes are accurate) took about <span style="font-weight: bold; color: rgb(0, 0, 0); background-color: rgb(255, 204, 204);">88</span> minutes to install from beginning to end (some of the time could have been eaten up in the "fetching" of the resource source files). Anyway, the same port on Leopard Server on the same machine with MacPort 1.6.0 took me roughly <span style="font-weight: bold; background-color: rgb(255, 204, 51);">20</span> minutes to install today. From 88 to 20 minutes is almost unheard of. I checked the port files too, to make sure the version of the gcc41 port I was installing was the same: <br><br>Tiger Server:<br><br><blockquote style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;" class="gmail_quote">gcc41 4.1.2, Revision 2, lang/gcc41 (Variants: universal, darwin_8, darwin_i386, powerpc, odcctools) <br></blockquote><br>Leopard Server:<br><br><blockquote style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;" class="gmail_quote">gcc41 4.1.2, Revision 2, lang/gcc41 (Variants: universal, darwin_8, darwin_i386, powerpc, odcctools) <br></blockquote><br>I presume this is because Leopard and Leopard Server are now leveraging the Apple Developer tools with a complete 64-bit wide architecture (both the hardware and the software)?<br></blockquote></div><div><br class="webkit-block-placeholder"></div><div><div>No, I think it's because Leopard's Tcl no longer searches an insane search path (including network volumes) as part of its startup. When we made this change in Leopard (largely because of pathological performance problems I noticed with MacPorts and fs_usage(1)), a full minute was shaved off the most basic port operations, including build/install (it's more observable with something like "port search").</div><div><br class="webkit-block-placeholder"></div><div>- Jordan</div><div><br class="webkit-block-placeholder"></div></div></div></body></html>