NVIDIA / NVIDIA/TensorRT

About device size and streaming budget size in TensorRT 10.7

Open
#4,285 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
13.4k
Forks
2.4k
Avg merge
5d 3h
Merged PRs (30d)
2

Description

Hi, I upgrade TensorRT from 8.4 to 10.7 and find several new interfaces about size get/set, I have some questions about them.

Following are involved interfaces:

  1. ICudaEngine::getDeviceMemorySizeV2
  2. ICudaEngine::getStreamableWeightsSize
  3. ICudaEngine::setWeightStreamingBudgetV2
  4. ICudaEngine::getWeightStreamingScratchMemorySize
  5. IExecutionContext::updateDeviceMemorySizeForShapes
  6. IExecutionContext::setDeviceMemoryV2

I tried to understand them according to comments but not for sure. Suppose kUSER_MANAGED is used for context creation and open weight streaming.

From 2 can find total weight size and user can calculate the budget size according to it and set through 3. And What does result of 4 do ? just a info ?

And for 1

  1. Does it should be called after 3?
  2. I think the return of it is the upper limit of total size, so 6 only need to set once using this return and there is no need to call 5 any more. is it right ? Otherwise, 6 should be called to set new buffer according to 5 return value every time new shapes have been set.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names six TensorRT interfaces but no source files, tests, or entry points. Start by reading the interface comments and the surrounding TensorRT 10.7 documentation for device-memory sizing, shape updates, and weight streaming; done means providing definitive lifecycle guidance for each listed call and clarifying the relationship between their returned sizes.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
machine-learning
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.