You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@mxnet.apache.org by GitBox <gi...@apache.org> on 2018/06/21 18:16:38 UTC

[GitHub] DickJC123 commented on issue #11341: Deterministic cudnn algorithms

DickJC123 commented on issue #11341: Deterministic cudnn algorithms
URL: https://github.com/apache/incubator-mxnet/issues/11341#issuecomment-399196667
 
 
   I prototyped this functionality last summer but did not PR it.  I found at the time that the regression suite would not run if only deterministic algorithms were permitted.  I'm not sure if the situation has improved in terms of universal coverage.  Some questions to think about:
   
   1. Assuming an environment variable, should it be MXNET_PREFER_DETERMINISM with a warning issued if no deterministic implementation exists, or MXNET_REQUIRE_DETERMINISM with a fatal error if no deterministic implementation exists?
   2. Should the directive be only for cudnn, or for the entire platform?
   3. Should the environment variable be setting a default, with new parameters added to the operators for individual operator instance control?
   4. What should the priority of determinism be relative to other constraints like "choose fastest algo" or "limit workspace"?  [Determinsim should win out I would think]

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services