<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:94595701;
mso-list-type:hybrid;
mso-list-template-ids:398334164 -1429323886 536870915 536870917 536870913 536870915 536870917 536870913 536870915 536870917;}
@list l0:level1
{mso-level-start-at:0;
mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;
mso-fareast-font-family:Calibri;
mso-bidi-font-family:"Times New Roman";}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="en-DE" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<ul style="margin-top:0cm" type="disc">
<li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level1 lfo1"><span lang="en-DE">Would it be possible to have some better support for those resource hungry tests, maybe a special jtreg test key ?<o:p></o:p></span></li></ul>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Hi, any suggestions / ideas ?<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">What about a key for tests consuming more than 4 G ( e.g. high_memory_consumption ) so that we can separate them and run them with less concurrency ?<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Best regards, Matthias<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="en-DE"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="mso-fareast-language:#2000">From:</span></b><span lang="EN-US" style="mso-fareast-language:#2000"> Baesken, Matthias
<br>
<b>Sent:</b> Thursday, 8 February 2024 14:40<br>
<b>To:</b> jtreg-dev@openjdk.org<br>
<b>Cc:</b> Zeller, Arno <arno.zeller@sap.com><br>
<b>Subject:</b> Jtreg test resource consumption issues<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="en-DE"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="en-DE">Hello, <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> </span><span lang="en-DE">we sometimes run into resource consumption issues when running the OpenJDK jtreg tests.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="en-DE">In our central test runs we try to set a reasonable conc level .<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="en-DE">However on some smaller test machines, or on test machines with other unpredictable corporate IT tools<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="en-DE">running at the same time and causing havoc, a couple of tests run into resource (especially memory) limitations.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="en-DE"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="en-DE">On Windows we see in these cases OOM crashes.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="en-DE">Something related is discussed here :<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="en-DE"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="en-DE"><a href="https://bugs.openjdk.org/browse/JDK-8324930">https://bugs.openjdk.org/browse/JDK-8324930</a><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="en-DE">8324930: java/lang/StringBuilder problem with concurrent jtreg runs<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="en-DE"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="en-DE">On AIX we see messages like "unexpected exit from test" or "Error invoking program" .<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="en-DE"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="en-DE">E.g.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="en-DE"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="en-DE">jdk/java/math/BigInteger/largeMemory/SymmetricRangeTests.java<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="en-DE"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="en-DE">29 * @requires (sun.arch.data.model == "64" & os.maxMemory >= 10g)<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="en-DE">30 * @run main/timeout=180/othervm -Xmx8g -XX:+CompactStrings SymmetricRangeTests<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="en-DE"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="en-DE">seems to be a candidate (also the other largeMemory tests).<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="en-DE"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="en-DE">Current approaches to "solve" this are rather poor :<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="en-DE">- reduce the concurrency of the jtreg tier - run; this leads to longer execution times of the tier than necessary,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="en-DE"> with only a few tests needing the lower concurrency<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="en-DE">- using exclusiveAccess.dirs (see also <a href="https://bugs.openjdk.org/browse/JDK-8324930">
https://bugs.openjdk.org/browse/JDK-8324930</a> ) - this is more a workaround and would<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="en-DE"> negatively impact other people running the tests with large machines<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="en-DE"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="en-DE">Would it be possible to have some better support for those resource hungry tests, maybe a special jtreg test key ?<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="en-DE">Currently there is a key "stress" but I am not sure if it is a good fit.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="en-DE">Or maybe have some evaluation of the "requires os.maxMemory" settings together with concurrency ?<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="en-DE">For example, run with a concurrency of 16 on a 32 G system; and in case a test with os.maxMemory larger some default occurs,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="en-DE">temporary reduce concurrency ?<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="en-DE"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="en-DE">Maybe there are already some options I did not consider ?<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="en-DE"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Best regards, Matthias<o:p></o:p></span></p>
</div>
</body>
</html>