[New-bugs-announce] [issue31695] Improve bigmem tests

Serhiy Storchaka report at bugs.python.org
Wed Oct 4 15:22:19 EDT 2017


New submission from Serhiy Storchaka <storchaka+cpython at 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 <report at bugs.python.org>
<https://bugs.python.org/issue31695>
_______________________________________


More information about the New-bugs-announce mailing list