On Sun, Mar 31, 2024, 18:44 Bruno Haible <br...@clisp.org> wrote: > NightStrike wrote: > > See https://bugs.gentoo.org/447970 for extra details. While this > > gentoo report has a workaround posted just a few months ago, it seems > > that the test itself is faulty, as a failure mode should not be to > > hang the entire computer. > > No. What I understand from the above ticket, is that the problem is > in the "libsandbox". > > Quote: "Also noticable on openvz guests, where getcwd test takes > about minute and without sandbox its below 3s." > > Quote: "The underlying problem appears to be that libsandbox's > mkdir() scales very poorly." > > Quote: "The slowness comes from glibc own getcwd calls. But this > isn't a problem when running outside sandbox ..." > > etc. > > Bruno >
Later on, there are data points that show that the algorithm is bad even outside the sandbox, it's just less noticeable. And as mentioned, on btrfs, it's crazy. In my setup, there is no sandbox. So sandboxing has nothing to do with the poor scalability of the function. >
