Skip to content
This repository has been archived by the owner on Oct 31, 2023. It is now read-only.

Why are training and testing so slow #48

Open
InstantWindy opened this issue Mar 6, 2023 · 2 comments
Open

Why are training and testing so slow #48

InstantWindy opened this issue Mar 6, 2023 · 2 comments

Comments

@InstantWindy
Copy link

Why are training and testing so slow?

@nuoran7607
Copy link

One possible reason is that most of the time is spent on reading images. Since there are so many images in ImageNet, it is best to use linux multiprocessing during training and testing (i.e. workers parameter is not set to 0, normal linux systems support workers parameter as 8). Another solution is to put training and test images on a solid-state drive, which can greatly increase the speed of reading images compared to a mechanical hard drive

@InstantWindy
Copy link
Author

I did not read the ImageNet dataset, but read the Cifar dataset

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants