[gmx-users] GMX 2018 regression tests: cufftPlanMany R2C plan failure (error code 5)
pall.szilard at gmail.com
Thu Feb 8 20:27:09 CET 2018
Note that the actual mdrun performance need not be affected both of it's
it's a driver persistence issue (you'll just see a few seconds lag at mdrun
startup) or some other CUDA application startup-related lag (an mdrun run
does mostly very different kind of things than this set of particular unit
On Thu, Feb 8, 2018 at 7:40 PM, Alex <nedomacho at gmail.com> wrote:
> I keep getting bounce messages from the list, so in case things didn't get
> 1. We enabled PM -- still times out.
> 2. 3-4 days ago we had very fast runs with GPU (2016.4), so I don't know if
> we miraculously broke everything to the point where our $25K box performs
> worse than Mark's laptop. That in itself might be publishable...
> 3. I will run tests on a system, for which I know the performance with
> 2016.4 so we can compare, especially with -pme gpu
> Gromacs Users mailing list
> * Please search the archive at http://www.gromacs.org/
> Support/Mailing_Lists/GMX-Users_List before posting!
> * Can't post? Read http://www.gromacs.org/Support/Mailing_Lists
> * For (un)subscribe requests visit
> https://maillist.sys.kth.se/mailman/listinfo/gromacs.org_gmx-users or
> send a mail to gmx-users-request at gromacs.org.
More information about the gromacs.org_gmx-users