DWORD "heap_chunk_in_mb" and CYGWIN_NT-5.2-WOW64
Sun Dec 19 22:38:00 GMT 2010
I need to revise my problem report some weeks ago. Actually, the "Changing
Cygwin's Maximum Memory" explanations under
regtool -i set /HKLM/Software/Cygwin/heap_chunk_in_mb 2048
regtool -v list /HKLM/Software/Cygwin
do work under Windows Server 2003 64bit. And exactly,
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Cygwin is that place where the
abovementioned regtool invocation will place "heap_chunk_in_mb".
Sorry for having bothered you some time ago, I did something wrong that
day (no idea what). The max_memory check program now returns 1792MB
Regards - Ulf-Dietrich
On Wed, 10 Nov 2010, Ulf-Dietrich Braumann wrote:
> it is maybe no surprise that the advice for changing cygwin's maximum
> memory given under http://www.cygwin.com/cygwin-ug-net/setup-maxmem.html
> does not work under Windows Server 2003 64bit, i.e. the max_memory.c
> check program always returns 1536MB available memory, no matter if I
> place the DWORD "heap_chunk_in_mb" (I want 2048MB) in the
> HKEY_LOCAL_MACHINE or the HKEY_CURRENT_USER registry branch. And yes, I
> always have restarted the whole server to give cygwin a chance to read
> the variable.
> During my search I have found some Cygwin entries in a branch
> HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Cygwin, so I have tried to place
> the "heap_chunk_in_mb" there, but got no effect.
> Does anybody know where to correctly place the DWORD "heap_chunk_in_mb"
> on a Windows Server 2003 64bit running CYGWIN_NT-5.2-WOW64?
> Thanks a lot - Ulf-Dietrich
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
More information about the Cygwin