Usability issues when using BladeDISC to compile GPT3
Open
- Dominant language
- C++
- Stars
- 933
- Forks
- 169
- PR merge metrics
- No merged PRs in 30d
Description
**Describe**
We meet some usability issues when using BladeDISC to compile GPT3. Track them here:
- [ ] Performance issue @tanyokwok @qiuxiafei @JamesTheZ
- [ ] BladeDISC compilation's time is too long @wyzero @tanyokwok
- [ ] The model is too large to success save to the file @tanyokwok @qiuxiafei
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files, tests, or entry points. Start by reproducing GPT3 compilation with BladeDISC and separate the performance, compilation-time, and model-saving reports; done means each checklist item has a measured resolution and the model saves successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- compilers, machine-learning, performance
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100