Test drive of the 6/06 Solaris 10 part 2, usage

The machine is up. If you don’t know about Blastwave, it is a helpful resource. Once you set up your machine, mozy over there, and get all the tools you would otherwise be missing.

Linux 40.9 Solaris 109 Hmmm. Something doesn't seem quite right. If I build HMMer as a 32 bit application under Linux, it takes about 82s on this test. I wonder if the Sun compilers don't build 64 bit binaries by default (they should). Dig around in the docs, play with some options. Finally come up with-fast -xarch=amd64a -xvector=simd -xdepend -xO5after reading the release notes, the man pages, etc. Rut it again. Here are the results. Platform Time (s)

Linux 40.9 Solaris 57.6 ` The Solaris code is definitely 64 bit this time. Note that Opterons do run 64 bit code faster due to the memory address models (flat versus segmented), as well as having more registers available in 64 bit mode, as well as having more SSE registers available … Why the Solaris compilers don’t generate this by default is not obvious. I will need to ask. Note that I wanted to try this with the 64 bit gcc for Solaris x86_64, only to discover that there was no such beast. This is not a comprehensive test. Hard to draw general conclusions from it. It does match experience that I and others have had with other codes. I will likely get another hard disk or two in the unit, try out Nextenta and Windows 2003 64 bit server. I have higher hopes for Nextenta. If it lives up to them, it could make a good platform to build clusters from for people who insist upon a Solaris kernel for some reason. For those who don’t know, Nextenta is the Solaris kernel with the Debian application stack. I haven’t heard of too many customers demanding Solaris based clusters. The only ones that I am aware of are the ones that bought into the SCO FUD (curiously boosted by both Microsoft and Sun). Eventually we will try out WCC. Again, we haven’t heard of customers seeking to go this route. Likely there will be a few.