Is cudnn necessary when TensorRT is used to run inference?


It’s a little weird to ask this question but I am confused.

I use command ldd to check, but there is no link to cudnn but has one. It seems ok to run inference only linking to

And I also check in TensorRT-, it needs cudnn.


  1. What‘s the differences between and
  2. Is that ok to run inference only linking but no cudnn offered ?

ldd (0x00007ffc04544000) => /lib/x86_64-linux-gnu/ (0x00007fb413687000) => /lib/x86_64-linux-gnu/ (0x00007fb413681000) => /lib/x86_64-linux-gnu/ (0x00007fb41349f000) => /lib/x86_64-linux-gnu/ (0x00007fb413350000) => /lib/x86_64-linux-gnu/ (0x00007fb413335000) => /lib/x86_64-linux-gnu/ (0x00007fb413141000)
    /lib64/ (0x00007fb42d9ee000) => /lib/x86_64-linux-gnu/ (0x00007fb41311e000)


TensorRT Version: TensorRT-

Can you try running your model with trtexec command, and share the “”–verbose"" log in case if the issue persist

You can refer below link for all the supported operators list, in case any operator is not supported you need to create a custom plugin to support that operation

Also, request you to share your model and script if not shared already so that we can help you better.

Meanwhile, for some common errors and queries please refer to below link:


I am sorry but there is no error issues. It’s the question about dynamic linking TensorRT in project that make me confused.


Sorry for the delayed response. is the actual TensorRT runtime. is a collection of TensorRT of open-source plugins that are available here, GitHub - NVIDIA/TensorRT: TensorRT is a C++ library for high performance inference on NVIDIA GPUs and deep learning accelerators. .

Those plugins are only required to implement some special ONNX operations and are not necessary for every TRT engine.

It is possible to forbid CUDNN tactics (e.g. using this flag of trtexec ).

  --tacticSources=tactics     Specify the tactics to be used by adding (+) or removing (-) tactics from the default 
                              tactic sources (default = all available tactics).
                              Note: Currently only cuDNN, cuBLAS and cuBLAS-LT are listed as optional tactics.
                              Tactic Sources: tactics ::= [","tactic]
                                              tactic  ::= (+|-)lib
                                              lib     ::= "CUBLAS"|"CUBLAS_LT"|"CUDNN"

Thank you.