Details
-
Task
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
A lot of tests are using too much resources on the test suite. An example would be a compacting test unbounded using 1.5G of memory in executors because it is not using any syncs in the journal and it just keeps throwing more stuff on executors, or another case would be certain MQTTTests or Certificate tests.
We should be careful and if we really must use that many resources we should then move the test into a soak test.
I have recently added a few commits as NO-JIRA, which was a mistake from my part as I thought it was going to be an easy task but this has been extending as a major task.
here is a list of commits I have added as part of this issue:
commit 41b2ec7efbc05955402ed94e2a120932dc6dab0b
Author: Clebert Suconic <clebertsuconic@apache.org>
Date: Tue Mar 28 04:38:15 2023 -0400
NO-JIRA Limitting load on PotentialOOMELoggingTest
commit 6de9e30c4638d8ac50d4088a65f0c700527b3ba9
Author: Clebert Suconic <clebertsuconic@apache.org>
Date: Tue Mar 28 04:33:24 2023 -0400
NO-JIRA Limiting load on NIOJournalCompactTest
commit 880fe86ddc35adb681832440ab589736312edd84
Author: Clebert Suconic <clebertsuconic@apache.org>
Date: Mon Mar 27 17:45:00 2023 -0400
NO-JIRA Moving MQTT5Test::testMaxMessageSize into a soak-test
commit d139ad75c2edff8a9ab765e907d3d6eb090492a7
Author: Clebert Suconic <clebertsuconic@apache.org>
Date: Mon Mar 27 12:30:33 2023 -0400
NO-JIRA Allocating less memory on soak-tests
commit 95cba558e41ab60a015c38384214d4ed20320b64
Author: Clebert Suconic <clebertsuconic@apache.org>
Date: Mon Mar 27 09:18:55 2023 -0400
NO-JIRA Allocating less memory on soak-tests
commit d730d1a684c6868ba24745c1ccd220c14b84c74f
Author: Clebert Suconic <clebertsuconic@apache.org>
Date: Thu Mar 16 20:36:09 2023 -0400
NO-JIRA Testsuite speedup: proper JDBC drop from derby
