Closed Junjun-NOAA closed 1 month ago
Those ctest times include waiting time in the queue. Hera has been quite slow for me recently so I am guessing that is the problem. Typically the longest ctest is the GETKF solver which takes about ~20 minutes of actual runtime (it will be reduced to ~10 min after we can use reduce obs space
).
Part of the increased wait time too is probably due to requesting 30 min for the mpas-jedi ctests. The increased wall time is really only needed for the GETKF solver so I plan to tune those a bit better whenever I update the OOPS hash (after this PR is merged).
ctest takes 35919.88 sec. Is it an issue related to HPC?
@ShunLiu-NOAA Yes, as @SamuelDegelia-NOAA mentioned, this was because Hera was known to have a very long job waiting time recently. The ctests themselves don't have any issues.
Part of the increased wait time too is probably due to requesting 30 min for the mpas-jedi ctests. The increased wall time is really only needed for the GETKF solver so I plan to tune those a bit better whenever I update the OOPS hash (after this PR is merged).
Thanks for the thought. I don't think 10 minutes vs 30 minutes will make any evident differences in RDHPCS, :)
Part of the increased wait time too is probably due to requesting 30 min for the mpas-jedi ctests. The increased wall time is really only needed for the GETKF solver so I plan to tune those a bit better whenever I update the OOPS hash (after this PR is merged).
Thanks for the thought. I don't think 10 minutes vs 30 minutes will make any evident differences in RDHPCS, :)
I wouldn't think so, but 5 min vs 30 min is currently making a big difference. The fv3-jedi tests that request 5 min here are not waiting at all and run within a few minutes. But the mpas-jedi tests that request 30 min are waiting much much longer.
Part of the increased wait time too is probably due to requesting 30 min for the mpas-jedi ctests. The increased wall time is really only needed for the GETKF solver so I plan to tune those a bit better whenever I update the OOPS hash (after this PR is merged).
Thanks for the thought. I don't think 10 minutes vs 30 minutes will make any evident differences in RDHPCS, :)
I wouldn't think so, but 5 min vs 30 min is currently making a big difference. The fv3-jedi tests that request 5 min here are not waiting at all and run within a few minutes. But the mpas-jedi tests that request 30 min are waiting much much longer.
Good to know. If it helps, you may go ahead to make the changes. Thanks.
Good to know. If it helps, you may go ahead to make the changes. Thanks.
I plan to wait until we update the OOPS hash further. We'll need to do that first to get the lower run times for GETKF (via reduce obs space
). Hopefully I can start on that as soon as this PR gets merged.
@hu5970 Do you get a chance to review this PR?
@ShunLiu-NOAA @hu5970 Do we still lingering issues on this PR? Otherwise, we should consider merging this PR. Thanks!
@guoqing-noaa I will ask the team on this PR tomorrow and try to arrange an order to merge the PRs.
List of submodule changes. issue #193