Title: Improve bigmem tests
Type: enhancement Stage:
Components: Tests Versions:
Status: open Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: pitrou, serhiy.storchaka, vstinner
Priority: normal Keywords:

Created on 2017-10-04 19:22 by serhiy.storchaka, last changed 2017-10-07 15:45 by pitrou.

Messages (2)
msg303729 - (view) Author: Serhiy Storchaka (serhiy.storchaka) * (Python committer) Date: 2017-10-04 19:22
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.
msg303885 - (view) Author: Antoine Pitrou (pitrou) * (Python committer) Date: 2017-10-07 15:45
+1 to all this :-)
Date User Action Args
2017-10-07 15:45:09pitrousetnosy: + pitrou
messages: + msg303885
2017-10-04 19:22:19serhiy.storchakacreate