You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Let's use this Issue to track performance issues and enhancement requests, so it's easier to prioritize the work.
This is for pytorch transformers
Also I will label it as a Good Difficult Issue in case someone is ready for a challenging but rewarding experience of figuring things out. If you do want to take the challenge comment in the corresponding Issue/PR that resonates with you so others would know you're working on it.
If I missed any other relevant open performance-related Issues/PRs that need attention please comment below.
Regression:
[WIP] FSMT bart-like refactor #11218 Regression after Bart-like refactoring - need to compare the original Bart refactoring PR since most likely the regression happened there.
stas00
changed the title
[Performance] Tracking open Issues and PRs
[Performance] Tracking open Issues and PRs (pytorch)
Jun 12, 2021
stas00
changed the title
[Performance] Tracking open Issues and PRs (pytorch)
[Performance] Tracking open Issues and PRs (pytorch transformers)
Jun 12, 2021
@stas00 If I want to work on this issue, should I pick one of those issues to keep track of its performance?
Can you also tell me how I can keep track of the performances? Can you give me some guidance?
Hi @JuheonChu, this is not an Issue to work on. As the title says this is a collection of pointers to track other Issues. It's dated but many issues that it links to are still valid. So you can click on the issue that resonates with you and discuss the details there - not here.
Let's use this Issue to track performance issues and enhancement requests, so it's easier to prioritize the work.
This is for pytorch
transformers
Also I will label it as a
Good Difficult Issue
in case someone is ready for a challenging but rewarding experience of figuring things out. If you do want to take the challenge comment in the corresponding Issue/PR that resonates with you so others would know you're working on it.If I missed any other relevant open performance-related Issues/PRs that need attention please comment below.
Regression:
Odd slowness:
--fp16_full_eval
is 25% slower #10816 figuring out why eval with --fp16_full_eval is 25% slowerFused kernels possibilities:
Faster / leaner startup / module loading
from_pretrained
skip storage allocation #12274 - skip storage allocation which gets dropped for pretrained weightsFaster optimizers
MemoryEfficientFP16Optimizer
from fairseqtorch.optim._multi_tensor
faster optimizers #9965 -torch.optim._multi_tensor
faster optimizers - having some bottleneck in the test script - need to profileScalability
Deepspeed-specific features
from_pretrained
w/ zero3 #12273 - makefrom_pretrained
loading fasterTests
The text was updated successfully, but these errors were encountered: