You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
hi, Giovanni, I just re-implemented the MG-2D on my dataset and met with some other bug for cpu explosion.
When I used MG for pre-training, I found that the utilization rate of the CPU would increase strangely, but the utilization rate of the GPU fluctuated greatly, and the buzzer of the machine PC would alarm soon. After several rounds of debugging, I found that it was this piece of code that caused the CPU utilization to sharply increase to 4000%+!!!!
I don't know why, but after changing np.dot in function : nonlinear_transformation and related calculations to torch, the CPU utilization has returned to normal (200%+).
Maybe this is a special case in my machine, and it has no reference value.
Thanks. :-)
The text was updated successfully, but these errors were encountered:
hi, Giovanni, I just re-implemented the MG-2D on my dataset and met with some other bug for cpu explosion.
When I used MG for pre-training, I found that the utilization rate of the CPU would increase strangely, but the utilization rate of the GPU fluctuated greatly, and the buzzer of the machine PC would alarm soon. After several rounds of debugging, I found that it was this piece of code that caused the CPU utilization to sharply increase to 4000%+!!!!
ModelsGenesis/pytorch/utils.py
Line 45 in 1393252
I don't know why, but after changing np.dot in function : nonlinear_transformation and related calculations to torch, the CPU utilization has returned to normal (200%+).
Maybe this is a special case in my machine, and it has no reference value.
Thanks. :-)
The text was updated successfully, but these errors were encountered: