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

Could you tell me the hardware information for the experiment? #4

Closed
BlueGhostZ opened this issue Mar 27, 2021 · 4 comments
Closed

Comments

@BlueGhostZ
Copy link

Thank you very much for openning source.
I'd like to ask about the hardware of your experiment (GPU, memory size, etc.). Looking forward to your reply.

@BlueGhostZ
Copy link
Author

@huangtinglin

@huangtinglin
Copy link
Owner

Sorry for the late reply. The experiments are conducted on a single Linux server with 512G RAM and 8 NVIDIA GeForce v100-32GB.

@BlueGhostZ
Copy link
Author

Thank you for your reply.In the training log of Amazon-Book dataset, the training time of eachepoch is 800+ seconds, which is unacceptable. I used to use the whole last.FM Data sets (3 million interactions and 460000 + triplets) and also use Tesla V100 to train KGAT, and the average train time of each epoch is only 182 seconds. KGIN has no additional knowledge Graph representation learning(e.g. transR). Why does it spend so much time training?

@huangtinglin
Copy link
Owner

I think the most time-consuming procedure is calculating the equation (7)(10), which is implemented in the "KGIN" file (line 35-38). Here I use the torch_scatter package to aggregate the neighbor embedding, and it can be further optimized or replaced by another efficient implementation.

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