3 ms·

You don't think an OS/kernel should be expected to perform the most basic of kernel tasks well? Also creating a lot of processes to run your tests is a perfect

You don't think an OS/kernel should be expected to perform the most basic of kernel tasks well? Also creating a lot of processes to run your tests is a perfectly normal use case. In this case they're running 10 per process, but creating 1 process/test (so as to not leave any corrupt memory/state behind after a failed one) would also be perfectly reasonable.

rightbyte 8y ago
Am I misunderstanding this; there are 1000 instances of a process stemming from a 120Mb executable, and initializing it 1000 times is kind off slow unless you chose to turn off some branching integrity check.
- nixpulvis 8y ago
  I don't think other OSs have this much trouble, but I haven't performed my own testing, so take this statement with a grain of salt.
  - rightbyte 8y ago
    Dunno. But reading the test readme it seems like gLinux (GNU/Linux? RS' new angle?) has other problems that need dehacking. I mean running test like this is fine who cares. But it's probably bad architecture for the unit test that makes it take time rather than the OSes. And that's fine because it's not production code. But not ground for a condescending snarky blog post. https://www.chromium.org/developers/testing/running-tests https://www.chromium.org/developers/testing/running-tests 'Run tests 5x faster on gLinux Browser tests on gLinux start up extremely slowly due to idiosyncratic NSS configurations. If you need to regularly run browser tests on gLinux, consider using the run_with_dummy_home.py helper script: testing/run_with_dummy_home.py testing/xvfb.py out/Default/browser_tests This can speed tests up by 5x or more.'
    - chmod775 8y ago
      That is something specific to gLinux, not Linux. Also it's not even related to the kernel. They're likely using some NSS configuration that does network lookups (maybe they're using NIS, LDAP or something else).
    - xyzzyz 8y ago
      gLinux is Google's internal Linux distribution, based on Debian.

rightbyte 8y ago

Am I misunderstanding this; there are 1000 instances of a process stemming from a 120Mb executable, and initializing it 1000 times is kind off slow unless you chose to turn off some branching integrity check.

nixpulvis 8y ago
I don't think other OSs have this much trouble, but I haven't performed my own testing, so take this statement with a grain of salt.
- rightbyte 8y ago
  Dunno. But reading the test readme it seems like gLinux (GNU/Linux? RS' new angle?) has other problems that need dehacking. I mean running test like this is fine who cares. But it's probably bad architecture for the unit test that makes it take time rather than the OSes. And that's fine because it's not production code. But not ground for a condescending snarky blog post. https://www.chromium.org/developers/testing/running-tests https://www.chromium.org/developers/testing/running-tests 'Run tests 5x faster on gLinux Browser tests on gLinux start up extremely slowly due to idiosyncratic NSS configurations. If you need to regularly run browser tests on gLinux, consider using the run_with_dummy_home.py helper script: testing/run_with_dummy_home.py testing/xvfb.py out/Default/browser_tests This can speed tests up by 5x or more.'
  - chmod775 8y ago
    That is something specific to gLinux, not Linux. Also it's not even related to the kernel. They're likely using some NSS configuration that does network lookups (maybe they're using NIS, LDAP or something else).
  - xyzzyz 8y ago
    gLinux is Google's internal Linux distribution, based on Debian.