-
Notifications
You must be signed in to change notification settings - Fork 78
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
Diagnose & Speed-up Hypergraph tutorials #215
Comments
Excellent, thanks for the very detailed diagnosis. I agree with all your points and the solutions. iv. I like the naive solution of reducing the number of epochs from 5 to 1, together with a comment in the text explaining that in real applications that number should be increased. i-iii. These are awesome solutions, but would take more time. Maybe we can deprioritize them for now? (there are a lot of other tasks remaining). |
@ninamiolane |
Independently of this issue, I also wanted to know if Sunday is a reasonable target to resolve all (or most in case of getting totally stuck in an issue) issues assigned to me? |
Even better if you can do iii as well, thanks for offering! Sunday is a perfect target of deadline 💯 Thanks for your great and fast work. |
Thanks a lot! |
@ninamiolane I fell ill after my travel back from India last week, so couldn't meet the timeline that I gave earlier. Sorry for that! I will try to complete all the issues asap. Thanks a lot for your consideration. |
Thanks for the heads-up, and sorry to hear that you feel ill. Stay safe! |
@devendragovil any update on this? |
@ninamiolane Oh I am really sorry for the late response. I have raised a PR for this issue, run-times are now around 5.5-6 mins. I am stuck at one thing for a long time, it will help reduce overall run-time by 1-1.5 mins, but this PR helps reduce most of the time. |
What?
Testing the tutorials on hypergraphs takes ~15 minutes, whereas testing the tutorials on other domains takes ~2-5 minutes (see screenshot).
There is probably one tutorial on hypergraphs that takes very long and slows down the whole github action workflow.
Find out which one and whether it can be accelerated.
Why?
A slow testing workflow slows down all the contributors, who have to wait for all tests to pass before being able to move on.
The text was updated successfully, but these errors were encountered: