Is convolution node 486 in Faster R-CNN working fine?
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 9.8k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
Bug Report
Which model does this pertain to?
Model faster R-CNN Opset 12
Describe the bug
I am doing profiling with faster RCNN and calculating the Throughput in TOPs is 1321 TOPs which is really high over the limits of the NVIDIA A100 GPU. Can somebody explain me if the model works properly?
Reproduction instructions
System Information
OS Platform and Distribution (Linux Ubuntu 22.04):
ONNX version (1.14):
Backend/Runtime version (Onnexruntime 1.15):
Here my profiling data:
FP32
dur: 70
486_kernel_time
output_type_shape: ( 1, 256, 200, 392)
input_type_shape: (1, 256, 200, 392)
kernel_shape : (256, 256, 3, 3)
bias: 256
provider: CUDAExecutionProvider
op_name: Conv
Throughput: 1321 TOPs
Notes
A100 specs is: Peak FP32 TFLOPS (non-Tensor) = 19.5
Contributor guide
No contributing guide indexed for this repository
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
Start with the Faster R-CNN Opset 12 model and the provided profiling data for convolution node 486. Reproduce the profile on Ubuntu 22.04 with ONNX 1.14, Onnxruntime 1.15, and CUDAExecutionProvider, then compare the reported throughput with the node's shapes and kernel duration. Done means explaining whether the measurement is valid and identifying any profiling issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ubuntu
- Domain
- computer-vision, machine-learning, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100