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
There are several places in the hail batch code where machine memory is not reported exactly/ correctly. For azure instances, the 64 Core E machines are said to have 8192 mib per core of memory which is incorrect. The machine has 504 Gib = 516096 Mib of memory, which equates to 516096/64 = 8064 mib per core. The other E instances do indeed have 8192 mib per core.
In gcp, the highcpu machines are said to have 924 mib per core which is not correct either. These machines do not have in integer number of mib per machine. The code that calculates their memory should be evaluated to see if the rounding is being done appropriately.
Version
0.2.130
Relevant log output
No response
The text was updated successfully, but these errors were encountered:
What happened?
There are several places in the hail batch code where machine memory is not reported exactly/ correctly. For azure instances, the 64 Core E machines are said to have 8192 mib per core of memory which is incorrect. The machine has 504 Gib = 516096 Mib of memory, which equates to 516096/64 = 8064 mib per core. The other E instances do indeed have 8192 mib per core.
In gcp, the highcpu machines are said to have 924 mib per core which is not correct either. These machines do not have in integer number of mib per machine. The code that calculates their memory should be evaluated to see if the rounding is being done appropriately.
Version
0.2.130
Relevant log output
No response
The text was updated successfully, but these errors were encountered: