On Sat, 2009-08-15 at 00:03 -0700, Sriram Natarajan wrote: > > Stefan Teleman wrote: > > Danek Duvall wrote: > >> Roland Mainz wrote: > >> > >>> The question is "why are longer build times be painfull" ? > >> > >> Because the official builds machine already take 10+ hours to build > >> all of > >> SFW. If a nightly is broken for any reason, the turnaround time to > >> get a > >> good build out is a long time. > >> > >> Again, it may still be worth the pain, but the cost of doing this is not > >> free, so we should take some care in the analysis of what needs to be > >> optimized, and to what degree. > > > > I have a (somewhat theoretical) question about the potential > > performance benefit we could get by tweaking the compiler optimization > > flags in this particular case: > > > > The discussion here seems to be centered around software which is used > > by WebStack applications -- and specifically some graphics libraries. > At this point, I have not identified any web stack specific applications > or libraries. I am very interested in cpu intensive libraries like > libgd, libjpeg etc - which are very CPU intensive. When I meant with > "optimized compiler options" - I meant to enable it to build it with > SSE2 and other cpu flags so that the generated code can take advantage > of these modern CPU. Af course, I wonder - who is going to install > OpenSolaris these days in pre-pentium cpu's that we don't enable these > flags by default. But, I don't want to get into that discussion now. > > Af couse, now that OpenSSL is coming to SFW,
It's been in SFW since 117. > I am sure, crypto libraries > can possibly benefit as well if it is compiled for modern cpu. We do deliver amd64 binaries which take advantage of a lot of hand-coded assembly using SSE2 etc. For 32bit x86 I recently enabled a lot of hand-coded asm howver I forced it to 386 compatibility mode. Its still 1.5-3 times faster in some cases (AES, RSA) than the old c-only code. To see the affect on SSH speed have a look at http://blogs.sun.com/mbp/entry/big_speed_ups_for_openssl (short version: ssh is now 1.85x faster). There is 32bit asm available for OpenSSL which could take advantage of SSE2 etc and I'm considering delivering it. The clear win on recent modern machines for OpenSSL though is to move to 64bit - I would imagine that this is generally true. -M
