ISC 07

Wish I was there. Have an injured foot, recovering slowly. Not sure what I did. Aside from that, costs to fly into Dresden were huge. Looked at Frankfurt, Berlin, Prague … Ugh. Maybe next year.
Microsoft PR sent me some information pointers, I invited them to post here. Hopefully they will. I want adoption numbers. Looking over the PR and thinking it through, if they were having a massive adoption, I think that would be what they would talk about. If they were having a few successes in a limited domain, thats what they would talk about. And this appears to be the case.

Looks like the financial service folks, who are probably running .NET for the most part, have no trouble using formalized clusters rather than an array of desktops. This makes sense, and would be a slam dunk IMO.
The flip side of this are on the canned application side. This list does not look significantly longer than the list at launch last year. Which suggests not outright neglect on the part of ISVs but a wait-and-see attitude. On this list you have standard commercial offerings, some open-source-turned-commercial, and some long time windows desktop folks. I don’t see any bright new exciting names there.
ISVs want to know, if they spend their own money to build and ship a windows cluster enabled application, that they will at minimum, break even, and far more importantly, make a growing profit. Simple economics/business. What is the ROI. In some cases, and I would argue for the vast majority on the list, the “I” was already done. It was a recompile away from WCC certification. Now put a new app on. This is where the porting expense comes from.
This is something, BTW, that we have tried to talk to Microsoft about in the past, when they asked us to propose running benchmarks for them. We pointed out that there was a little matter of a port and optimization to the target first. I am not quite sure they grasp how large this barrier is, and why this is preventing more applications from getting on there.
If your applications are already running on windows desktops, running on clusters may or may not be worth your while, the “I” has largely been paid for, its simply a question of marginal additional “R”. If your application runs on Linux clusters, that “I” is going to be huge, like it or not. So that “R” had better be as well. Most ISVs recognize that it won’t be. Hence Microsoft’s problem. And this brings up another point that I have tried to raise.
The business case. WCC is not better, cheaper, faster. It is more expensive, less well developed/vetted, and in a fair number of cases likely slower. When we went in front of VCs in the past we were asked is our accelerator product a “gotta have”, a “would like to have”, or “nice to have”, or “yet another one”. In retrospect, our answer of “gotta have” was correct, though we weren’t believed at the time. But lets ask the same question of WCC. Is it a “gotta have”? I don’t think so. If you do a SWOT analysis of it relative to its competitors, its only strength is that it is windows. Its weaknesses are legion, its opportunities are selling to its pre-converted masses, those running clusters on desktop systems. Its threats are a better faster cheaper competitor with more mindshare which is driving the market forward.
Next company stockholder meeting, would someone please ask Microsoft what it is they are doing? If you are at ISC, please ask them about this. I want to know the adoption rates. I want to know their level of commitment. I want to know how they are going to lower the barriers to application porting. None of this is trivial.
Disclosure: My families IRA and likely my relatives 401k’s have Microsoft stock.

3 thoughts on “ISC 07”

  1. Joe – thanks for freeing up the comments section. I couldn’t find my user name/password last week, then was out of the office for a bit. So this is much more convenient.
    This is going to be a two-part response. The second part will include comments (directly from them, or cut/paste by me) from vendors who have done the port to Windows. I have emails out to commercial and academic partners seeking comments/input to your post. Hopefully it will drive a good discussion.
    The first part here is a bit of a state of the union. Windows CCS has been in the market for 11 months. There are no YoY comparisons available to see adoption rates. But since we’re starting from a low installed base for HPC, suffice it to say our growth rate will be large. There are those folks who used Windows Server 2003 (prior to CCS) and Windows 2000 Server for HPC applications. Cornell Theory Center, Perlegen Sciences, HSBC are a few that come to mind.
    Of course MSFT doesn’t publicly report absolute sales/shipment figures for individual server products. So how do I prove customer adoption? I can point you to the 15 case studies: . Note that two of those case studies are with ISVs: LSTC and ANSYS. I also can point to customers cited in prior PR, marketing collateral. Suffice to say, in 11 months we’ve had enough customers buy Windows CCS that there will be a version 2 and broaded engineering, sales, marketing efforts.
    In terms of supply, let’s look at the OEMs. All of the main server vendors (absent Hitachi) have adopted and sell Windows CCS. I’m not saying they sell more of Windows CCS than Linux … that’s not the case. But Dell, IBM, HP, SGI, Bull, Fujitsu, NEC have sales/marketing initiatives for Windows CCS … some stronger than others.
    Next is the networking vendors … Windows CCS is agnostic and supports them all. I believe Mellanox and Cisco were involved with our Top500 benchmarks.
    In terms of applications, the Year 1 goal was to get the top commercial ISVs in each target industry (e.g., ANSYS/Fluent, Schlumberger, Parallel Geo, LSTC, Dassault, Wolfram, MSC, CD-adapco) and the core horizontal ISVs (e.g., MathWorks, Platform). There are new ISVs and universities porting codes to Windows; these include CMG, University of Tennessee, PipeLine, SPT, Roxar, AutoDesk. New scripts and codes are posted to the community site on Technet: , and on Ken’s site: . Admittedly, we don’t yet have the volume of Linux, but we’re committed to get there.
    In terms of application porting, I know that some ISVs are opting to use Subsystem for UNIX-based applications (SUA), which comes with Windows Server 2003. I believe NCAR used SUA when it ported WRF to Windows. SUA is a posix tool similar to CYGWIN, which also has been used to do ports. Also, more and more vendors are pushing their Fortran compiler to Windows with integration in Visual Studio 2005 (Intel, PGI), which helps port the libraries and get away from the command line build that Windows users do not much appreciate. And I believe Persistence Software is doing a port to Windows.
    OK, that’s it for part 1. It’s a sunny day in Redmond and time to take advantage of it. I’ll be back in touch with comments/input from software vendors/universities.
    Update [ed]: cleaned up links so you don’t get spurious commas and periods

  2. Hi Patrick
    Thanks for the comment. With Cygwin, we have done some ports, but have observed significant performance drops in doing so. I am not sure that SFU would give us much better/worse.
    Most of the vendors you indicate are already existing vendors on Windows. It is no surprise to see them on CCS.
    The code porting issue is a significant one. Native ports will almost always (rare exceptions) give you better performance with good compilers. More importantly native ports are better coupled to the platform, less baggage in the way.
    Also important is the 32 vs 64 bit issue. Several windows folks I have spoken to don’t believe their is a performance difference between 32 bit and 64 bit code. This is incorrect. There is a difference, and it can be quite significant. We were measuring and reporting on this in 2003/2004 time frames.
    All this said, the PGI compiler is the most interesting aspect. As long as we can get a POSIX wrapper around it, porting should be a little easier. Its that POSIX wrapper that doesn’t seem to be of interest to Microsoft. You would prefer native, yet the barriers to porting POSIX code/environments is large.
    All of the above vendors you have cited (well most of them) have initiatives for Itanium2 systems as well. This is not a non-sequitur, I am pointing out that they have (most of them anyway) backed other platforms that have not lead to a success on that platform. After years of trying to gain traction, all but a few have given up on that platform. The rationale for giving up on the platform had to do with a mixture of disappointed sales volume, coupled with a better, cheaper, faster product available in the market. You may be able to buy Itanium2 systems well into the future. They just are not part of most of the successful vendors major platforms in HPC (save a few who made critical errors in judgement nearly a decade ago).
    I am also aware that Microsoft provides some sort of marketing $$$ to these folks for signing up. I am sure they will all push the platform hard.
    I looked over the scripting site. Ouch. You really have to know windows internals to be able to write these things. Painful. Also, some … uh … advocacy in there with jabs at telnet and ssh being “inconsistent”. As they are designed for different purposes, decades apart, yeah, it is possible that they are “inconsistent”. Since most cluster admins would use rsh or ssh, and they are effectively interchangable, well …
    Anyway, I do look forward to the rest of the reply.

  3. Joe – ISVs have been slower than expected to reply. I had asked folks from IBM, Cd-adapco, CMG and Univ of Tennessee to comment. No word yet, though IBM and UofT said they’d provide me something. I’ll follow-up with them when I return to the office from paternity leave in August.

Comments are closed.