From: Meik Frischke <meik.frischke@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] libreoffice-bin-3.4.5.2 broken ?
Date: Sun, 19 Feb 2012 13:57:51 +0100 [thread overview]
Message-ID: <2935411.1S4U0apQcn@picard> (raw)
In-Reply-To: <201202191226.59994.michaelkintzios@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1302 bytes --]
Am Sonntag, 19. Februar 2012, 12:26:57 schrieb Mick:
> On Sunday 19 Feb 2012 11:45:25 Neil Bothwick wrote:
> > On Sun, 19 Feb 2012 12:58:35 +0200, Thanasis wrote:
> > > > [root@hactar ~ 0]% genlop -t libreoffice
> > > >
> > > > * app-office/libreoffice
> > > >
> > > > Wed Feb 15 10:23:58 2012 >>> app-office/libreoffice-3.5.0.3
> > > >
> > > > merge time: 40 minutes and 52 seconds.
> > >
> > > Impressive. What's your hardware configuration, Neil?
> >
> > Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz with 16GB RAM.
>
> Hmm ... I've got a 1st generation i7 on my laptop and it is no-where near
> that fast. :-(
>
> Intel(R) Core(TM) i7 CPU Q 720 @ 1.60GHz with 4G RAM.
>
>
> Sun Jan 29 21:47:46 2012 >>> app-office/libreoffice-3.4.5.2
> merge time: 1 hour, 34 minutes and 43 seconds.
>
> Is it just down to the CPU or are you running /var/tmp/portage on some
> turbo- charged fs?
IO does really slow down the compilation progress a lot. Having PORTAGE_TMPDIR
on tmpfs saves about half an hour (compared to reiserfs on a 7200rpm disk) for
me :
Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz
Thu Feb 16 17:42:35 2012 >>> app-office/libreoffice-3.5.0.3
merge time: 50 minutes and 39 seconds.
With 4GB Ram thats not an option for you though...
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-02-19 13:00 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-18 9:39 [gentoo-user] libreoffice-bin-3.4.5.2 broken ? Jacques Montier
2012-02-18 12:41 ` Nilesh Govindrajan
2012-02-18 12:54 ` Neil Bothwick
2012-02-18 13:01 ` Nilesh Govindrajan
2012-02-18 16:53 ` Neil Bothwick
2012-02-18 13:43 ` Jacques Montier
2012-02-18 13:51 ` Dale
2012-02-18 14:05 ` Jacques Montier
2012-02-18 14:21 ` Dale
2012-02-18 14:42 ` Alan McKinnon
2012-02-18 15:17 ` Jacques Montier
2012-02-18 16:57 ` Neil Bothwick
2012-02-18 19:57 ` Alan McKinnon
2012-02-19 10:58 ` Thanasis
2012-02-19 11:45 ` Neil Bothwick
2012-02-19 12:26 ` Mick
2012-02-19 12:52 ` Neil Bothwick
2012-02-19 12:57 ` Meik Frischke [this message]
2012-02-19 14:36 ` Mick
2012-02-19 14:40 ` Alecks Gates
2012-02-19 12:50 ` [gentoo-user] " Hartmut Figge
2012-02-19 12:54 ` Alan McKinnon
2012-02-19 13:05 ` Hartmut Figge
2012-02-19 15:21 ` Hartmut Figge
2012-02-20 14:55 ` [gentoo-user] " Stefan G. Weichinger
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=2935411.1S4U0apQcn@picard \
--to=meik.frischke@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