public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jeremy Olexa <olexa@cs.umn.edu>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Compile question
Date: Sun, 16 Jul 2006 22:30:18 -0500	[thread overview]
Message-ID: <44BB044A.8090803@cs.umn.edu> (raw)
In-Reply-To: <44BAFB5A.6090802@gt.rr.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Anthony E. Caudel wrote:
> I have an AMD 64x2 with MAKEOPTS set to -j3.
> 
> I have noticed that some compiles (glibc for example) will use the
> system to the fullest. top reports %CPU near 0%.  Other compiles, such
> as openoffice seem to use only half as much cpu time.  For this top
> reported consistently near 50%.
> 
> So I'm wondering if the openoffice compile used only one of the amd
> cores.  Do some of the emerges ignore the MAKEOPTS setting?  Or is this
> an upstream issue with the compile not using threads?
> 
> Tony

Tony,
Some ebuilds filter out MAKEOPTS="-jX" because the makefile(?) is not
written correctly to compile with more than one concurrent compile
process. According to the OOo ebuild, -jX is not filtered, so that is
not the case. Also, you may have checked the CPU usage when it was
extracting the tarball, obviously the choke point here would be the HD,
not the CPU.

Just some extra info for you, I am not the ebuild expert. HTH

- --
Jeremy Olexa
(olexa@cs.umn.edu)
Office: EE/CS 1-201
CS/IT Systems Staff
University of Minnesota

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.4 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEuwRJFN7pD9kMi/URAsCSAJwMXoPA1fqg5CHkJxbId0OYsCXEcACeKXGc
r9FcluQ/XA0fRm8nBzTzmK4=
=goWq
-----END PGP SIGNATURE-----
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2006-07-17  3:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-17  2:52 [gentoo-user] Compile question Anthony E. Caudel
2006-07-17  3:30 ` Jeremy Olexa [this message]
2006-07-17  3:56   ` Donnie Berkholz

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=44BB044A.8090803@cs.umn.edu \
    --to=olexa@cs.umn.edu \
    --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