public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Paul Hartman" <paul.hartman+gentoo@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: progress everywhere !
Date: Mon, 20 Oct 2008 09:59:25 -0500	[thread overview]
Message-ID: <58965d8a0810200759g2b1e3210oda245c27f94dd0e7@mail.gmail.com> (raw)
In-Reply-To: <20081019164837.GA4594@ca.inter.net>

On Sun, Oct 19, 2008 at 11:48 AM, Philip Webb <purslow@ca.inter.net> wrote:
> 081019 Grant Edwards wrote:
>> On 2008-10-19, Alan McKinnon <alan.mckinnon@gmail.com> wrote:
>>> On Sunday 19 October 2008 07:25:28 Philip Webb wrote:
>>>> OO 3.0.0 compiled successfully in   2 h 29 m  on this Core2 Duo machine,
>>>> but needed  5,3 GB  temporary disk space (ok here, but others beware).
>>> The first time I build OOo (on a 686 amd) it took 12 hours.
>>> Now I get similar to you - 2h14
>> On some of my machines it still takes 12+ hours.
>
> On my back-up machine (AMD 2500+ , memory 1 GB : 2003), 2.4.1 took  > 5 hr .
> My everyday box (Core 2 Duo 2650 , memory 2 GB (faster FSB) : 2007),
> OO 2.4.1 took  2 h 14 m , so 3.0.0 is a bit more time-consuming;
> the download is much more:  346 MB  against  c 200 MB
> (that doesn't include the wretched Xulrunner:  75 MB  &  15 m  to compile).
> I suspect there wb pleas for help from users who run out of disk space:
> earlier versions needed  < 3 GB , so this is a big jump,
> esp as I have  2 GB  memory (I didn't check how much it was using).

On my system (Core 2 Duo E6600, overclocked to 3GHz) my OOo times were:

     Tue Aug 19 20:47:26 2008 >>> app-office/openoffice-2.4.1
       merge time: 2 hours, 43 minutes and 43 seconds.

     Fri Oct 17 21:22:31 2008 >>> app-office/openoffice-3.0.0
       merge time: 1 hour, 33 minutes and 40 seconds.

So the 3.0.0 compile is definitely faster by a lot for me. In 2.4.1 I
was able to use my 4 gig /dev/shm for my portage_tmpdir, but for 3.0.0
i had to comment out and use disk for temporary files. Maybe it could
have been even faster.

Thanks,
Paul



  parent reply	other threads:[~2008-10-20 14:59 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-19  5:25 [gentoo-user] progress everywhere ! Philip Webb
2008-10-19  6:05 ` Philip Webb
2008-10-19  7:00   ` Dale
2008-10-19 20:23   ` KH
2008-10-19  9:01 ` Alan McKinnon
2008-10-19 16:23   ` [gentoo-user] " Grant Edwards
2008-10-19 16:48     ` Philip Webb
2008-10-19 18:15       ` Alan McKinnon
2008-10-19 20:27         ` KH
2008-10-19 23:39         ` Philip Webb
2008-10-20 14:59       ` Paul Hartman [this message]
2008-10-21 10:56     ` Neil Bothwick
2008-10-19 16:52   ` [gentoo-user] " Philip Webb
2008-10-19 17:58     ` Alan McKinnon
2008-10-20  6:25       ` Walter Dnes
2008-10-20 10:26       ` Erik Hahn
2008-10-20 10:35         ` Alan McKinnon
2008-10-20 16:02           ` Erik Hahn
2008-10-21 10:59     ` Neil Bothwick
2008-10-19 13:19 ` luis jure

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=58965d8a0810200759g2b1e3210oda245c27f94dd0e7@mail.gmail.com \
    --to=paul.hartman+gentoo@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /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