#1718 closed help (answered)

ideal resubmission frequency on ARCHER

Reported by: fpithan Owned by: um_support
Priority: normal Component: ARCHER
Keywords: resubmission, queue Cc:
Platform: ARCHER UM Version: <select version>

Description

I would like to reduce the time my jobs spend in ARCHER queues to speed up the experiment's total turnover. I am running the UM version 8.5 at N96, AMIP-type, using 96 cores and 12 cores per node. My current resubmission pattern is once per year. Would it be better to resubmit less frequently to exploit the maximum runtime per job, or more frequently to have shorter individual jobs? Or is one year already the ideal balance?

Change History (2)

comment:1 Changed 20 months ago by willie

Hi Felix,

If you login to ARCHER and type

qstat -q

you can see the time limits for each of the queues. You also need to know how long your current NRUN/CRUNS are taking: this is at the bottom of the leave file.

You could also experiment with increasing the processor count to see the effect on run time.

See also How do I do a UM continuation run?

Regards,

Willie

comment:2 Changed 20 months ago by willie

  • Resolution set to answered
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.