High latency of DEBUG level on Jupyter Notebook compared to real-time
Hi. I am currently using RunPod for the development of deep learning models for my study, however, the jupyter notebook has been too laggy and unresponsive that the debug level that really take 3 hours to complete, it took me 8 hours just to finish it. I feel ripped off. Is this normal?
Solution:Jump to solution
Hello. It seems the issue comes from the output cell during runtime. I had it on DEBUG logging level and it was overloading the system. I changed it to INFO level and turned off my ad blocker and it fixed the issue.
8 Replies
jupyter notebook training time = 3.77 hours
real time = 8 hours
this isnt fair
What does the Notebook do? Specifically the problematic cell(s?) I'm not sure what went wrong, but I'm happy to help you figure it out.
so the training task/cell takes 3.77 hours
Took 8 hours because of .. (is it laggy jupyter, long saving or..)?
laggy jupyterlab
so its because of slow connection
ithink there is one thread with the same problem
https://canary.discord.com/channels/912829806415085598/1369881761064030218
Solution
Hello. It seems the issue comes from the output cell during runtime. I had it on DEBUG logging level and it was overloading the system. I changed it to INFO level and turned off my ad blocker and it fixed the issue.
Leaving this for future purposes.
Thank you for posting a solution!
Glad. you got it figured out