Le 11/05/2022 à 10:19, Alessandro Molina a écrit :
As far as I understood, the idea is not to fully remove memory mapping, just turn the current mmap=True default arguments to mmap=False The goal is mostly to provide consistent behaviour for end users. At the moment users might face very different performances when they read locally or on a network filesystem like NFS, because we will try to use memory mapping on both. But there were users reports that trying to memory map on NFS lead to terrible performances. By disabling memory mapping by default we can offer a more consistent experience to users.
Ideally we should be able to detect local vs. remote filesystems, but there doesn't seem to be an easy way to do that.
