deepspeedai / deepspeedai/DeepSpeedExamples
DeepSpeed not actually reduce wall clock time for 1 epoch - DCGAN
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6.8k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 1
Description
Hi,
I have successfully run the DCGAN training code using deepspeed, using the celeba dataset.
But the problem is when I run the baseline code, the training clock time also the same as deepspeed-enabled code (137s). So I don't know whether something I am missing now.
My system information is:
OS: Ubuntu 14.04
CUDA Toolkit 10.1.243
GPU: Single GPU - NVIDIA TiTanX
Pytorch version is 1.4.0, and also tested on 1.7.1
Thank you.
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 DCGAN training code and compare the baseline and DeepSpeed-enabled execution paths using the reported single-GPU setup. Measure the one-epoch wall-clock behavior and inspect the training configuration and timing points; done means identifying why both runs take about 137 seconds and documenting the relevant change or limitation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, pytorch
- Domain
- machine-learning, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100