New submission from Serhiy Storchaka <storchaka+cpyt...@gmail.com>: I think that the process of running bigmem tests should be improved.
1. Every bigmem test should run in separate process. It's effect on memory fragmentation shouldn't affect other tests. 2. Only one bigmem test should be run at the same time. Otherwise several parallel bigmem tests can exhaust RAM and lead to swapping. In multiprocessing mode the process running a bigmem test should send a signal to other processes, wait until they finished their current tests and paused, run a bigmem test, and send a signal to other processes that they can continue. 3. The hard limit of addressed memory should be set for every bigmem test, according to the declared requirements. It is better to crash one test and report the failure, than hang on swapping. 4. All other tests should be run with the limit set to 2 GiB (or 1 GiB?). This will help to find memory consuming tests which should be made bigmem tests. 5. The maxrss of the process running a bigmem test should be reported in verbose mode after finishing a test. ---------- components: Tests messages: 303729 nosy: haypo, serhiy.storchaka priority: normal severity: normal status: open title: Improve bigmem tests type: enhancement _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue31695> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
