| 1 |
On Friday 05 May 2006 16:06, Hans-Werner Hilse wrote: |
| 2 |
> Hi, |
| 3 |
> |
| 4 |
> On Fri, 5 May 2006 18:49:29 +0530 Farhan Ahmed |
| 5 |
> |
| 6 |
> <farhanahmed06@×××××.com> wrote: |
| 7 |
> > > The difference is: with -j2 box is slow. A lot of packages do not |
| 8 |
> > > compile because of ooms. |
| 9 |
> > > |
| 10 |
> > > with -j1 box is normal. No ooms. Compiling does not take longer as |
| 11 |
> > > with -j2. |
| 12 |
> > |
| 13 |
> > This is the first time I'm hearing this.. Even with -j2 my system |
| 14 |
> > functions normally.. Has anyone encountered same problem? |
| 15 |
> |
| 16 |
> Not really. GCC does eat some memory, but it's not that worse. Well, |
| 17 |
> this does absolutely depend on RAM+Swap. Whenever I had oom conditions |
| 18 |
> in the past 4 years, that was because of a leaky, long-running |
| 19 |
> application. I've yet to see a gcc process that claims 100MB of |
| 20 |
> physical memory. I did see Apache eat such an amount of mem after |
| 21 |
> running some days and calling leaky skripts (integrated as a module, of |
| 22 |
> course). |
| 23 |
> |
| 24 |
|
| 25 |
on AMD64 compiling kdepim or wesnoth, there are structures created, that takes |
| 26 |
700mb and more. And this is not even swappable. |
| 27 |
|
| 28 |
So with 1gig of ram, you can run into ooms. |
| 29 |
|
| 30 |
I had enough of them. Even on a fresh booted system with nothing running than |
| 31 |
the emerge process. That has nothing to do with flaky applications, just much |
| 32 |
ram needed by gcc. |
| 33 |
-- |
| 34 |
gentoo-user@g.o mailing list |
Archives