Changes between Version 29 and Version 30 of SourceCode/Performances/r3623
- Timestamp:
- 2016-10-12T10:43:47+02:00 (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
SourceCode/Performances/r3623
v29 v30 2 2 = ORCHIDEE performance (trunk revision 3623) = 3 3 4 == Table 1: Orchidee Scalability==4 == Orchidee scalability for different horizontal []resolutions == 5 5 Following table is based on tests with following set up: 6 6 * Simulation length: 1Y … … 10 10 * Output level: monthly and daily output 11 11 * MPI parallelization 12 * while using XIOS, 64 cores simulation = 1 core MPI for the XIOS server + 63 cores MPIfor Orchidee executable12 * 1MPI is used for the server XIOS, the rest are used for Orchidee executable 13 13 * no server is used for 1 MPI case or for the case with IOIPSL 14 14 15 15 === Conclusion === 16 16 17 See in this table the recommended number of processes for a given resolution for global simulations with the corresponding CPU time for one year of simulation. 17 '''For the trunk ORCHIDEE it is recommended to use XIOS with 1 server. See in this table the recommended number of processes for a given resolution for global simulations with the corresponding CPU time for 10 years of simulation.''' The computing time is the same at curie and ada. 18 18 19 || = Forcing file resolution =||= Num. processes =||= Real computing time per 1 year =||= Total computing time per 1 year =||20 || 2 deg || 3 2p || 4m24 || 2h20||21 || 1 deg || 6 4p || 8m13 || 8h46||22 || 0.5 deg || 6 4p || 24m02 || 25h33||19 || Forcing file resolution || Recommended number of processes || Real computing time / 10 years || Total computing time / 10 years || 20 || 2 deg || 31 MPI orchidee + 1 MPI XIOS server || 43 m || 22 h || 21 || 1 deg || 63 MPI orchidee + 1 MPI xios server || 1 h 20m || 85 h || 22 || 0.5 deg || 63 MPI orchidee + 1 MPI xios server || 4 h || 260 h || 23 23 24 24 Note: The total(requested) computing time should be used in the demand for computing resources at TGCC and IDRIS. … … 26 26 The total cpu time is calculated by multiplying the real time with the numbers of MPI used. 27 27 28 === XIOS (using restart files) === 28 === Details === 29 ==== XIOS (using restart files) ==== 29 30 30 31 Reference simulation … … 37 38 *: Recommended number of processors 38 39 39 === XIOS (start without restart files)===40 ==== XIOS (start without restart files) ==== 40 41 41 42 XIOS only writes the history outputs files. … … 46 47 ||halfdeg || Not possible || Mem limit || 3h33 || 2h03 || 1h25 || 1h05 || 1h02 || 47 48 48 === IOIPSL (using restart files)===49 ==== IOIPSL (using restart files) ==== 49 50 50 51 || || 1 MPI || 4 MPI || 8 MPI || 16 MPI || 32 MPI || 64 MPI || 128 MPI || … … 53 54 ||halfdeg || >16h40 (max limit) || 6h23 || 3h50 || 2h08 || 1h17 || 50m34 || 36m45 || 54 55 55 === IOIPSL (start without restart files)===56 ==== IOIPSL (start without restart files) ==== 56 57 57 58 Only IOIPSL enabled. … … 64 65 65 66 66 == Table 2: Orchidee XIOS scalability (IO)- TODO - ==67 == Orchidee scalability to the output level - TODO - == 67 68 In this table the set up FG2.CWRR is used with 63MPI for orchidee_ol and 1MPI for the server XIOS. For the case with IOIPSL, then 64MPI are used for orchidee_ol. 68 69 The first line describes different levels of output.