'tensorrt_bindings.tensorrt.IBuilderConfig' object has no attribute 'max_workspace_size'
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 13.4k
- Forks
- 2.4k
- Avg merge
- 5d 3h
- Merged PRs (30d)
- 2
Description
Description
In various sections of the guide, particularly within the code examples and certain textual explanations, it is stated that one should specify the maximum workspace size using the config.max_workspace_size parameter during engine creation. However, in another part of the guide, it suggests utilizing config.set_memory_pool_limit(trt.MemoryPoolType.WORKSPACE, 1 << 20) for the same purpose.
This inconsistency has led to confusion in understanding the recommended approach for setting the maximum workspace size. It would be greatly appreciated if you could provide clarification on which method is the correct and recommended way to configure the workspace memory size during engine creation..
Environment
TensorRT Version: 10.0.06b
NVIDIA GPU: RTX3070
NVIDIA Driver Version: 12.1
CUDA Version: 12
CUDNN Version: 8.9.2
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Search the guide's engine-creation examples and explanations for config.max_workspace_size and config.set_memory_pool_limit(trt.MemoryPoolType.WORKSPACE, 1 << 20). Confirm the recommended TensorRT 10.0.06b approach and update the conflicting documentation so all references use the same method.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100