TensorRT Lean Best Practices #2349
Unanswered
joekale-pp
asked this question in
Q&A
Replies: 1 comment
|
I added a Draft PR to potentially address some of the packaging issues based on my understanding of the packages. #2357 |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
TensorRT Core libraries contain all of the functions to build, fine-tune, and compile model engine files. This is unnecessary bulk to the target filesystem for edge devices with no need to compile engines. To combat this Nvidia provides the "dispatch" and "lean" libraries where the "lean" allows a smaller footprint on the device.
Builds fail when you try to DEPEND on
tensorrt-core-leanso the solution I used to allow building was:tensorrt-coretoDEPENDStensorrt-corefromRDEPENDStensorrt-core-leanto theRDEPENDSMy current understanding is, the application only needs to link against
libnvinfer_leanfor runtime usage of that lean_runtime, or thedispatchcan be used to allow multpile runtimes to be deployed for engines not compiled for the exact lean_runtime.The engine also needs to be compiled on the same hardware, with the same set of libraries (full tensorrt-core required) but with the options
--versionCompatible --excludeLeanRuntimewith the latter keeping the runtime from being built into the engine.Is this the best way to achieve this? By adding tensortt-core to the DEPENDS all libraries end up in the sysroots which is good, but you have to manually remove the largest package manually from the RDEPENDS and add the smaller one to achieve the 750MB size reduction.
All reactions