Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

train speed #2

Open
easyfcn opened this issue Aug 1, 2020 · 1 comment
Open

train speed #2

easyfcn opened this issue Aug 1, 2020 · 1 comment

Comments

@easyfcn
Copy link

easyfcn commented Aug 1, 2020

dear ,why the POINT+GCN train speed is so slow??
I want to know your train speed.
thank you.

@chendaichao
Copy link
Owner

Thanks for your questions. The low training speed is mainly caused by the construction of input graph, where we need to compute all pairwise distances, determine the weights and pack these weights to a sparse adjacency matrix. I admit that this is really time-consuming; furthermore, since the data points are augmented by random rotation, the graph has to be reconstructed in every epoch.
In terms of the training speed, the training took about half an hour per epoch when n=1024 on a single GTX 1080Ti. When n=128 or 256 it run much faster, so indeed I first train the model with n=256, and tune it for larger n. I have also tried not using data augmentation and constructing the graph in the preprocessing stage. This really made it faster but the model seemed to overfit.
I think probably there would be a more efficient and elegant solution. If you find one, please share it with me.

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

No branches or pull requests

2 participants