Opened 3 years ago

Closed 3 years ago

#1943 closed help (answered)

HadGEM2-ES -- how fast

Reported by: simon.tett Owned by: um_support
Component: UM Model Keywords: HadGEM2-ES
Cc: Platform: ARCHER
UM Version: 6.6.3

Description

HI,

apologies for an urgent request. I am considering a proposal for the current 1.5K call and would like to do some model simulations. If I submit I'll be writing the proposal with a colleague over the next 48 hours… One possibility we are considering is using CESM 1.2.2 and an other possibility we are considering is to use HadGEM2-ES.

So on Archer (assuming 100% throughput) how fast does HadGEM2-ES run (the Earth System Model), how many nodes does it need and how many k AU/simulated year does it use? I recall that when we ran the climate model version of HadGEM2 that ran at about 2 simulated years/day on Monsoon — but that was some time ago..

Secondary question — what versions of the UM is HadGEM2-ES available at?

many thanks
Simon

Change History (3)

comment:1 Changed 3 years ago by ros

Hi Simon,

The only figures I can get my hands on immediately is when we ported to ARCHER originally and it was only a very short run, so may not be much use.

HadGEM2-ES running on 12x8 cores (4 nodes): 3 days, dumping every day took 00:05:32 which cost 132 AUs.

HadGEM2-ES is UM version 6.6.3

I just tried re-running my HadGEM2-ES job and it's fallen over, but if I get any further figures by the end of today I'll send them on.

Cheers,
Ros.


comment:2 Changed 3 years ago by simon.tett

Hi Ros,

thanks. We decided not to go ahead so I don't think it is worth you spending time. I think that means that HadGEM2-ES does a day in about 2 minutes. Or 1 year in ½ a day ⇒ 2 simulated years/day. That's quite poor. CESM does more like 10 years in 1 day at 2x2 resoln… I can use that is someone pops at my choice of CESM in a standard proposal…

Simon

comment:3 Changed 3 years ago by ros

  • Resolution set to answered
  • Status changed from new to closed
  • UM Version changed from <select version> to 6.6.3
Note: See TracTickets for help on using tickets.