Skip to content
This repository was archived by the owner on Nov 17, 2023. It is now read-only.
This repository was archived by the owner on Nov 17, 2023. It is now read-only.

How to disable MXNET_CUDNN_AUTOTUNE_DEFAULT and bucketing log message without turning off MXNET_CUDNN_AUTOTUNE_DEFAULT? #8132

Description

@yxchng

16:49:37] src/operator/././cudnn_algoreg-inl.h:112: Running performance tests to find the best convolution algorithm, this can take a while... (setting env variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[16:49:37] src/operator/././cudnn_algoreg-inl.h:117: If you see this message in the middle of training, you are probably using bucketing. Consider setting env variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disabl
e cudnn tuning.
[16:49:42] src/operator/././cudnn_algoreg-inl.h:112: Running performance tests to find the best convolution algorithm, this can take a while... (setting env variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[16:49:42] src/operator/././cudnn_algoreg-inl.h:117: If you see this message in the middle of training, you are probably using bucketing. Consider setting env variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disabl
e cudnn tuning.
[16:49:42] src/operator/././cudnn_algoreg-inl.h:112: Running performance tests to find the best convolution algorithm, this can take a while... (setting env variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[16:49:42] src/operator/././cudnn_algoreg-inl.h:117: If you see this message in the middle of training, you are probably using bucketing. Consider setting env variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disabl
e cudnn tuning.
[16:49:42] src/operator/././cudnn_algoreg-inl.h:112: Running performance tests to find the best convolution algorithm, this can take a while... (setting env variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[16:49:42] src/operator/././cudnn_algoreg-inl.h:117: If you see this message in the middle of training, you are probably using bucketing. Consider setting env variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disabl
e cudnn tuning.
[16:49:45] src/operator/././cudnn_algoreg-inl.h:112: Running performance tests to find the best convolution algorithm, this can take a while... (setting env variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[16:49:45] src/operator/././cudnn_algoreg-inl.h:117: If you see this message in the middle of training, you are probably using bucketing. Consider setting env variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disabl
e cudnn tuning.
[16:49:47] src/operator/././cudnn_algoreg-inl.h:112: Running performance tests to find the best convolution algorithm, this can take a while... (setting env variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[16:49:47] src/operator/././cudnn_algoreg-inl.h:117: If you see this message in the middle of training, you are probably using bucketing. Consider setting env variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disabl
e cudnn tuning.
[16:49:49] src/operator/././cudnn_algoreg-inl.h:112: Running performance tests to find the best convolution algorithm, this can take a while... (setting env variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[16:49:49] src/operator/././cudnn_algoreg-inl.h:117: If you see this message in the middle of training, you are probably using bucketing. Consider setting env variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disabl
e cudnn tuning.
[16:49:49] src/operator/././cudnn_algoreg-inl.h:112: Running performance tests to find the best convolution algorithm, this can take a while... (setting env variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[16:49:49] src/operator/././cudnn_algoreg-inl.h:117: If you see this message in the middle of training, you are probably using bucketing. Consider setting env variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disabl
e cudnn tuning.
[16:49:51] src/operator/././cudnn_algoreg-inl.h:112: Running performance tests to find the best convolution algorithm, this can take a while... (setting env variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[16:49:51] src/operator/././cudnn_algoreg-inl.h:117: If you see this message in the middle of training, you are probably using bucketing. Consider setting env variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disabl
e cudnn tuning.
[16:49:52] src/operator/././cudnn_algoreg-inl.h:112: Running performance tests to find the best convolution algorithm, this can take a while... (setting env variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[16:49:52] src/operator/././cudnn_algoreg-inl.h:117: If you see this message in the middle of training, you are probably using bucketing. Consider setting env variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disabl
e cudnn tuning.
[16:49:52] src/operator/././cudnn_algoreg-inl.h:112: Running performance tests to find the best convolution algorithm, this can take a while... (setting env variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[16:49:52] src/operator/././cudnn_algoreg-inl.h:117: If you see this message in the middle of training, you are probably using bucketing. Consider setting env variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disabl
e cudnn tuning.
[16:49:53] src/operator/././cudnn_algoreg-inl.h:112: Running performance tests to find the best convolution algorithm, this can take a while... (setting env variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[16:49:53] src/operator/././cudnn_algoreg-inl.h:117: If you see this message in the middle of training, you are probably using bucketing. Consider setting env variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disabl
e cudnn tuning.
[16:49:54] src/operator/././cudnn_algoreg-inl.h:112: Running performance tests to find the best convolution algorithm, this can take a while... (setting env variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[16:49:54] src/operator/././cudnn_algoreg-inl.h:117: If you see this message in the middle of training, you are probably using bucketing. Consider setting env variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disabl
e cudnn tuning.
[16:49:55] src/operator/././cudnn_algoreg-inl.h:112: Running performance tests to find the best convolution algorithm, this can take a while... (setting env variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[16:49:55] src/operator/././cudnn_algoreg-inl.h:117: If you see this message in the middle of training, you are probably using bucketing. Consider setting env variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disabl
e cudnn tuning.
[16:49:55] src/operator/././cudnn_algoreg-inl.h:112: Running performance tests to find the best convolution algorithm, this can take a while... (setting env variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[16:49:55] src/operator/././cudnn_algoreg-inl.h:117: If you see this message in the middle of training, you are probably using bucketing. Consider setting env variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disabl
e cudnn tuning.

Activity

  1. changed the title [-]How to disable MXNET_CUDNN_AUTOTUNE_DEFAULT log message without turning off MXNET_CUDNN_AUTOTUNE_DEFAULT?[/-] [+]How to disable MXNET_CUDNN_AUTOTUNE_DEFAULT and bucketing log message without turning off MXNET_CUDNN_AUTOTUNE_DEFAULT?[/+] on Oct 3, 2017
  2. yxchng commented on Oct 3, 2017

    @yxchng
    Author

    I tried exporting or using os.environ but they don't work. The code i am using is https://github.com/pangyupo/mxnet_mtcnn_face_detection

  3. szha commented on Oct 5, 2017

    @szha
    Member

    #7988 ought to do it.

  4. yxchng commented on Oct 5, 2017

    @yxchng
    Author

    @szha I don't quite understand how to use #7988. How should I solve the problem?

  5. szha commented on Oct 5, 2017

    @szha
    Member

    Sorry for the confusion. What I meant was that once that PR is merged the problem should be resolved. Let's wait for that PR to get in first.

  6. stupidZZ commented on Oct 13, 2017

    @stupidZZ

    I have the same problems for that.

  7. kli-casia commented on Dec 5, 2017

    @kli-casia
    Contributor

    @yxchng did you save this problem, i am also using mtcnn mxnet

  8. guker commented on Dec 11, 2017

    @guker

    export MXNET_CUDNN_AUTOTUNE_DEFALUT=0, it is ok

  9. jrzaurin commented on Dec 29, 2017

    @jrzaurin

    Hi there

    I am on Ubuntu 16.04.3 using conda 4.4.2 and Python 2.7.14

    I see the same error even after export MXNET_CUDNN_AUTOTUNE_DEFALUT=0

    ubuntu@ip-10-0-0-14:$ export MXNET_CUDNN_AUTOTUNE_DEFALUT=0
    ubuntu@ip-10-0-0-14:$ python fine_tune_vgg.py --vgg nets/vgg16 --checkpoints checkpoints --prefix vggnet
    [20:56:31] src/io/iter_image_recordio_2.cc:153: ImageRecordIOParser2: ../datasets/rec/train.rec, use 1 threads for decoding..
    [20:56:36] src/io/iter_image_recordio_2.cc:153: ImageRecordIOParser2: ../datasets/rec/val.rec, use 1 threads for decoding..
    [INFO] loading pre-trained model...
    [20:56:37] src/nnvm/legacy_json_util.cc:190: Loading symbol saved by previous version v0.8.0. Attempting to upgrade...
    [20:56:37] src/nnvm/legacy_json_util.cc:198: Symbol successfully upgraded!
    [INFO] training network...
    [20:56:37] src/operator/././cudnn_algoreg-inl.h:112: Running performance tests to find the best convolution algorithm, this can take a while... (setting env variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
    

    Any news on how to solve this?

  10. szha commented on Dec 29, 2017

    @szha
    Member

    @jrzaurin This bug should have already been fixed by the PR mentioned above. Which version of mxnet are you using? Would you be able to upgrade to 1.0?

  11. jrzaurin commented on Dec 29, 2017

    @jrzaurin

    @szha

    In fact I am using

    In [2]: mxnet.__version__
    Out[2]: '0.11.0'
    

    which I installed via:
    pip install mxnet-cu80==0.11.0

    (opencv and graphviz where already installed)

    I upgraded to cuDNN v6.0 but I doubt that has something to do (?)

    Overall: Ubuntu 16.04.3, conda 4.4.2, Python 2.7.14 and mxnet 0.11 and I see the same message (I am running it as I write and is there) and it runs very very slow on a tiny dataset (Stanford Cars Dataset)

    so...any idea is appreciated, Thanks!

  12. szha commented on Dec 29, 2017

    @szha
    Member

    The latest version of mxnet is mxnet-cu80==1.0.0.post2. Would you be able to try out this version?

  13. jrzaurin commented on Dec 30, 2017

    @jrzaurin

    @szha

    Hey thanks!

    I did not know about the mxnet-cu80==1.0.0, updated on my p2 instance (Tesla K80) and my mac and the message is gone, so I assume that problem solved 👍

    Still runs very slow, but I am sure this is something on my side...so, regarding to the MXNET_CUDNN_AUTOTUNE_DEFALUT message, the solution was to upgrade:

    pip install mxnet-cu80==1.0.0

    and the message disappeared

    thanks!

    EDIT
    @szha

    just updated to mxnet-cu80==1.0.1 and:

    train_net.py:92: DeprecationWarning: mxnet.model.FeedForward has been deprecated. Please use mxnet.mod.Module instead.
      begin_epoch=10)
    /home/ubuntu/anaconda2/lib/python2.7/site-packages/mxnet/model.py:573: DeprecationWarning: Calling initializer with init(str, NDArray) has been deprecated.please use init(mx.init.InitDesc(...), NDArray) instead.
      self.initializer(k, v)
    /home/ubuntu/anaconda2/lib/python2.7/site-packages/mxnet/model.py:579: DeprecationWarning: Calling initializer with init(str, NDArray) has been deprecated.please use init(mx.init.InitDesc(...), NDArray) instead.
      self.initializer(k, v)
    [16:21:55] src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:107: Running performance tests to find the best convolution algorithm, this can take a while... (setting env variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
    

    The first 3 lines are just DeprecationWarning, but the final one is again the MXNET_CUDNN_AUTOTUNE_DEFAULT message even though is set to 0. Anyway, All seems to work fine, and it runs in decent times.

    I am just saying in case is useful.

  14. lanking520 commented on Apr 2, 2018

    @lanking520
    Member

    @yxchng , is this still an issue for you?

  15. yxchng commented on Apr 3, 2018

    @yxchng
    Author

    @lanking520 nope thanks

  16. canpeng78 commented on Apr 14, 2018

    @canpeng78

    I'm using mxnet 1.2.0, cuda 9.0 and cudnn 7.0, and still encounter this problem. So what's the final solution? (resetting MXNET_CUDNN_AUTOTUNE_DEFAULT doesn't work).
    Thanks!

  17. arisliang commented on Apr 18, 2018

    @arisliang

    While auto tuning, it gives an error message and still running. Is this normal? mx 1.2.0, cuda 9.0, ubuntu 16.04

    2605:2644:0418/091830.114475:ERROR:upload_data_presenter.cc(73)] Not implemented reached in virtual void extensions::RawDataPresenter::FeedNext(const net::UploadElementReader &)

    After export MXNET_CUDNN_AUTOTUNE_DEFAULT = 0, this error was gone.

  18. HX1079299660 commented on Nov 16, 2018

    @HX1079299660

    I have the same problems for now

  19. sbharadwajj commented on Feb 5, 2019

    @sbharadwajj

    The problem still persists after export MXNET_CUDNN_AUTOTUNE_DEFAULT = 0, running on mxnet 1.3.1, cuda 9.0, ubuntu 18.
    Help would be really appreciated.

  20. reopened this on Feb 5, 2019
  21. apeforest commented on Feb 21, 2019

    @apeforest
    Contributor

    Can you check in your model, if some convolution layer has cudnn_tune not set to off. If so, please update your model by setting all the cudnn_tune param all the layers to off. Thanks.

  22. joanshen0508 commented on Aug 26, 2021

    @joanshen0508
    1. you should revise your model file (*.json). Modify "cudnn_tune": "limited_workspace", to "cudnn_tune": "None",
    2. add
      import os
      os.environ['MXNET_CUDNN_AUTOTUNE_DEFAULT'] = '0'
      it works for me.
  23. locked and limited conversation to collaborators on Aug 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions