From: "Amidon, William H." <wamidon@middlebury.edu>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Cc: "Amidon, William H." <wamidon@middlebury.edu>
Subject: enabling /largeaddressaware for cygwin in windows 7 64-bit
Date: Thu, 04 Aug 2011 15:20:00 -0000 [thread overview]
Message-ID: <8C8430B888BACD4E91AC1CBE7000204F1D74558C@FISHERCAT.middlebury.edu> (raw)
Hello,
I am not a programming expert, and i wonder if you could give me some basic advice.
I am running cygwin on a 64-bit Dell XPS, running Windows 7, with a Core i5 processor, and 12 GB of RAM installed.
The fortran 90 code I am running keeps running out of memory (virtual memory or stack overflow errors) on jobs that the computer should easily handle. I have increased the paging memory to 36 MB, but I am afraid that CygWin is still being limited to ~ 1 GB of memory.
My problem is very similar to what is described here:
http://cygwin.com/ml/cygwin/2011-01/msg00196.html
I followed the instructions at [1] and [2] to increase the heap chunk available to cygwin, but I have also read that adding a /largeaddressaware link might further increase the amount of memory available to cygwin (see [3], which confused me a lot). I have not been able to find clear instructions about how to do this for cygwin, could you help?
Also, I am interested in any tips about how to maximize the amount of memory available to cygwin given my 64-bit windows 7 setup! Thanks very much for your kind help to a very helpless geologist!
Will Amidon
[1] http://www.cygwin.com/cygwin-ug-net/setup-maxmem.html
[2] http://cygwin.com/ml/cygwin/2010-04/msg00983.html
[3] http://www.cygwin.com/ml/cygwin-developers/2011-06/msg00002.html
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next reply other threads:[~2011-08-04 15:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-04 15:20 Amidon, William H. [this message]
2011-08-04 15:54 ` Corinna Vinschen
2011-08-04 17:37 ` Charles Wilson
2011-08-04 18:17 ` Corinna Vinschen
2011-08-04 22:17 ` Charles Wilson
2011-08-05 6:33 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8C8430B888BACD4E91AC1CBE7000204F1D74558C@FISHERCAT.middlebury.edu \
--to=wamidon@middlebury.edu \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).