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
The availableCores() function queries CGroups for CPU limits. It supports both CGroups v1 and CGroups v2. However, it does not handle hosts that have both CGroups v1 and CGroups v2 enabled at the time. When such a host is discovered, a warning is produced;
This warning means that it detected that both CGroups v1 (cgroups) and CGroups v2 (cgroups2) were discovered on the current machine, but that the current implementation does not know how to navigate that and will simply ignore both of them. One reason for not support this case is that I do have access to a machine is configured this way.
Now, today, @skertberg reported (futureverse/future#758) that they experienced this on one of their machines, which provides an opportunity to implement support for this mixed case.
@skertberg, I've updated the internals of parallelly to allow us to gather some more information about your CGroups v1+v2 setup, which would allow me to start working on this. Could you please install parallelly (>= 1.41.0-9004) by calling:
This saves a file cgroups.tar.gz to the current directory. Could you please send that file to me? That way I'll be able to implement and test support for your machine too.
The text was updated successfully, but these errors were encountered:
The
availableCores()
function queries CGroups for CPU limits. It supports both CGroups v1 and CGroups v2. However, it does not handle hosts that have both CGroups v1 and CGroups v2 enabled at the time. When such a host is discovered, a warning is produced;This warning means that it detected that both CGroups v1 (
cgroups
) and CGroups v2 (cgroups2
) were discovered on the current machine, but that the current implementation does not know how to navigate that and will simply ignore both of them. One reason for not support this case is that I do have access to a machine is configured this way.Now, today, @skertberg reported (futureverse/future#758) that they experienced this on one of their machines, which provides an opportunity to implement support for this mixed case.
@skertberg, I've updated the internals of parallelly to allow us to gather some more information about your CGroups v1+v2 setup, which would allow me to start working on this. Could you please install parallelly (>= 1.41.0-9004) by calling:
Then, after restarting R, call:
This saves a file
cgroups.tar.gz
to the current directory. Could you please send that file to me? That way I'll be able to implement and test support for your machine too.The text was updated successfully, but these errors were encountered: