int8 quantization refinement for convolution
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- cpp
- Domain
- machine-learning, performance
Research direction
Start by reading PR #881, which removed the int8x4 packing for rocblas GEMM, then locate the convolution path that still performs this packing. Compare its rocblas call requirements for MI100 and verify that convolution int8 quantization no longer incurs the packing overhead.
Written by the indexing model from the issue text.
Description
Current implementation of the int8 convolution needs to pack input data to int8x4 data format, which is similar to the int8x4 data format requirement as the rocblas api. This packing is very slow, which make the int8 quantization is slower than fp16. From rocblas version 2.38 (maybe rocm4.0, software) and mi100 (hardware), this int8x4 data format requirement is not needed anymore.
We made the changes to remove the packing procedure for calling to rocblas (PR#881), so int8 gemm is supposed to running better on mi100 than before. We also need to make the change related to the convolution.
This issue is to track that changes.
- Dominant language
- C++
- Stars
- 333
- Forks
- 150
- Avg merge
- 4d 19h
- Merged PRs (30d)
- 54
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.
More from ROCm/AMDMIGraphX
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ROCm/AMDMIGraphX#5101 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 62/100
ROCm/AMDMIGraphX#3592 ·
-
status: triage
ROCm/AMDMIGraphX#5237 · 1 assignee ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
ROCm/AMDMIGraphX#5235 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
ROCm/AMDMIGraphX#5234 · 1 comment · 1 reaction ·
All issues in ROCm/AMDMIGraphX
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Sensor initialization takes very long when `--initial-sim-time` is set to current UNIX timestamp Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
gazebosim/gz-sensors#662 · 1 comment ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
LadybirdBrowser/ladybird#12123 ·