<!DOCTYPE html><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
On 04/01/2024 15:57, Viraj Shetty wrote:<br>
<blockquote type="cite" cite="mid:361A9308-7714-4F09-AF8C-3FA94CEA19B6@hxcore.ol">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style>@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;}p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}.MsoChpDefault
{mso-style-type:export-only;}div.WordSection1
{page:WordSection1;}</style>
<div class="WordSection1">
<p class="MsoNormal">:<br>
</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Does windows not allocate the 1M stack
memory per thread upfront ? Does windows not have upper limit
to process memory (It was using 5G memory) ? And how is the
java process continuously creating platform threads when the
machine memory is maxed out ? </p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Any insight on this behavior is appreciated
– though these look more like Windows questions.</p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</blockquote>
<br>
I read Mark Russinvich's blog on "Pushing the limits of Windows:
Processes and Threads" [1] a few years ago and found it useful to
understand what Windows reserves and commits.<br>
<br>
-Alan<br>
<br>
[1]
<a class="moz-txt-link-freetext" href="https://techcommunity.microsoft.com/t5/windows-blog-archive/pushing-the-limits-of-windows-processes-and-threads/ba-p/723824">https://techcommunity.microsoft.com/t5/windows-blog-archive/pushing-the-limits-of-windows-processes-and-threads/ba-p/723824</a><br>
</body>
</html>