This site is migrating to a new forum software on Tuesday, September 24th 2019, you may experience a short downtime during this transition

Main menu


Multiple questions: CCSM3 vs 3.5, Intel 11 compilers & patches

2 posts / 0 new
Last post
Multiple questions: CCSM3 vs 3.5, Intel 11 compilers & patches

Hi guys,

This is several questions all in one:

1) We're running CCSM3 (beta14) here - I know of the internal CCSM3.5, though. Is this something we should consider? I know from a long-ago look at things, the build system was changed considerably and might be much easier to use. I'm mostly interested in knowing what the major differences in performance are as well as how different CCSM3.0 and 3.5 are scientifically. I know that's a big question, so even if the answer is, "If you don't know, you don't want it!", that's fine. Just wanted to ask. ;-)

2) In another post on this board, Karen showed instructions for using the 10.1 Intel compilers - I'm planning on going to 11.0 and a preliminary test showed some issues, most of which I'm sure are pretty simple to work out. (And some system ones, too, such as CLK_TCK -> CLOCKS_PER_SEC). If I'm going to put in the effort to patch these, is there someone at NCAR to whom I can send the fixes? Is that even of interest to people, or is 4.0 close enough to release that additional patches to 3.0 are not terribly interesting? (Assuming Intel 11.0 runs correctly, of course.)

3) Finally, I know Meng-Pai Hung, a PhD student at OSU, achieved about 13.17 years/day on an Opteron cluster as OSC for the T42_gx1v3 runs he was doing. Does anyone have any data on Xeon (Harpertown) systems? The memory subsystem is poor, so load-balancing on-node is tough, but it's got a decent FPU. I'd also love any Nehalem timings people have. And ORNL's "Jaguar" achieved 40 years/day, but I can't find what resolution that was achieved at, anyone know?

Thanks very, very much,
- Brian


Hmmm I am afraid I can't answer your questions as I am not an internal, but I am curious about this 3.5 version too... :P

With that error con CLOCKS_PER_SEC I just exchanged the mct part of the package with a fresh downloaded MCT and it worked just fine (at least on the first stages of compilation! heh)

Are there so much news between intel 10.x and 11?

Well, if you are running something on intel I really recommend you compiling with intel compilers. It let me thrust the old CCM3 15 times faster on a E5462 Xeon CPU (on a dual quad-core system). Being it 3 times faster on single processor and effectively (not theoric) 15 times faster if distributed on the 8 processors. I don't know if the statistics will give you good point to CCSM3, but measuring two months, they were done in 7 mins and 44 secs. This would be 31 years a day if I am right with my accounts. :P Resolution used was T42. Again, it is CCM3, old, unsupported.

Log in or register to post comments

Who's new

  • jwolff
  • tinna.gunnarsdo...
  • sarthak2235@...
  • eolivares@...
  • shubham.gandhi@...