From: Anna Sidera <sidera.anan@ucy.ac.cy>
To: "John S. Fine" <johnsfine@verizon.net>
Cc: gcc-help@gcc.gnu.org
Subject: Re: cannot run many programs simultaneously
Date: Thu, 04 Mar 2010 02:28:00 -0000 [thread overview]
Message-ID: <f5c6b503deb1.4b8f361b@ucy.ac.cy> (raw)
In-Reply-To: <4B8E9DCA.7080808@verizon.net>
When I said stop, I meant they stop running before finishing.
If increasing the swap space makes them vrey slow this will not help me. The reason I run 6 programms simultaneously is to save time.
Can you explain 'hit either the system over commit limit or actual exhaustion of memory'?
I will ask about this problem at the linux forum also.
Thanks,
Anna
----- Original Message -----
From: "John S. Fine" <johnsfine@verizon.net>
Date: Wednesday, March 3, 2010 7:35 pm
Subject: Re: cannot run many programs simultaneously
> As Ian already explained, you're asking in the wrong place,
> because
> there is no reason to believe this is a GCC issue.
>
> The programming or linux-general forums at LQ would be a better
> place if
> this discussion needs a lot of follow up.
> http://www.linuxquestions.org/questions/
>
> But for now, I'll give the basic answer:
>
> Anna Sidera wrote:
> > They run for some time and then they stop. However when I run
> only 3 of them simultaneously, and then run the other 3, they all
> finish successfully.
> >
> The obvious explanation for that behavior would be you hit either
> the
> system over commit limit or actual exhaustion of memory. Until
> you rule
> that out, you shouldn't look for any more obscure theory.
>
> Either one of those (over commit limit or exhaustion of memory)
> could be
> dealt with by increasing the amount of swap space in the system.
> If you
> lack enough physical memory to run 6 of those processes at once,
> increasing swap space would stop that from crashing, but might
> just make
> them crawl instead of crash. (Depending on what you mean by
> "stop",
> that might already be what you are experiencing. You may need to
> explain "stop" better in order to get a better answer).
> > I do not know if it is a bug or a problem with the memory the
> system allows me to use. The output of the ulimit -a command is
> the following:
>
> That isn't relevant. No matter what ulimit allows each process to
> use,
> it can't allow the total of all six processes to use more than is
> available for the whole system.
>
>
next prev parent reply other threads:[~2010-03-04 2:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-03 14:35 Anna Sidera
2010-03-03 15:48 ` Ian Lance Taylor
2010-03-03 17:35 ` John S. Fine
2010-03-04 2:28 ` Anna Sidera [this message]
2010-03-04 3:34 ` John (Eljay) Love-Jensen
2010-03-04 16:09 ` Anna Sidera
2010-03-04 16:58 ` Axel Freyn
2010-03-04 16:43 ` John S. Fine
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=f5c6b503deb1.4b8f361b@ucy.ac.cy \
--to=sidera.anan@ucy.ac.cy \
--cc=gcc-help@gcc.gnu.org \
--cc=johnsfine@verizon.net \
/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).