[gmx-developers] Please cancel outdated CI pipelines
erik.lindahl at gmail.com
Mon Sep 28 21:14:20 CEST 2020
Given that several other test containers finish in ~2 minutes, I think it's
relatively unlikely that random fluctuating resource contention would
systematically always affect the gmxapi test every time it is run, but no
other jobs :-)
The whole point of k8s/docker is that the runtime environment is
standardized; what performance do you see if you run the same container
e.g. on your laptop, desktop, or any other cloud resource when assigning
two hardware threads to it?
On Mon, Sep 28, 2020 at 8:38 PM Eric Irrgang <ericirrgang at gmail.com> wrote:
> > On Sep 28, 2020, at 6:00 PM, Erik Lindahl <erik.lindahl at gmail.com>
> > - gmx-api. They both take 12-15 minutes on two cores, and there are four
> of them.
> I think there is something wrong with the way resources are detected in
> the CI Kubernetes environment that is causing oversubscription. I think at
> least 90% of that time is due to resource contention. The jobs only take a
> few seconds when run locally. I've mentioned this a couple of times to Paul
> and Mark but we haven't been able to prioritize it. It sounds like Mark and
> I may take a closer look in October, but I can't troubleshoot effectively
> because the run-time environment is opaque to me.
> Otherwise, I agree.
> Gromacs Developers mailing list
> * Please search the archive at
> http://www.gromacs.org/Support/Mailing_Lists/GMX-developers_List before
> * Can't post? Read http://www.gromacs.org/Support/Mailing_Lists
> * For (un)subscribe requests visit
> or send a mail to gmx-developers-request at gromacs.org.
Erik Lindahl <erik.lindahl at dbb.su.se>
Professor of Biophysics, Dept. Biochemistry & Biophysics, Stockholm
Science for Life Laboratory, Box 1031, 17121 Solna, Sweden
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the gromacs.org_gmx-developers