public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Walter Dnes" <waltdnes@waltdnes.org>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] A tale of computing thud and blunder
Date: Sun, 18 Dec 2011 19:05:22 -0500	[thread overview]
Message-ID: <20111219000522.GA22397@waltdnes.org> (raw)
In-Reply-To: <jckg7m$cmn$1@dough.gmane.org>

On Sun, Dec 18, 2011 at 12:45:27PM +0200, Nikos Chantziaras wrote
>
> On 12/18/2011 12:34 PM, Walter Dnes wrote:
> >
> >    This was only recently installed.  Is it possible that the generic x86
> > code from the initial install was the problem?  And that emerging
> > system+world got me full optimization?
> 
> Could be.  It could also be it's because of "-mfpmath=sse".  That's only 
> used by default on 64-bit.  On 32-bit, the FPU is used for floating 
> point operations by default, which gives better precision (80 bit vs 64 
> bit) but slower speed.
> 
> But then again, that sounds too much of a performance difference.  So if 
> I had to guess, I'd say it's because of the world rebuild that made sure 
> everything was built with proper optimizations.

  It's probably the sum total of the effect of all the flags.  I've
renamed the thread, to be more accurate.  Here's how things went...

* right after the install (presumably with generic i686 code) the PC
  could not handle streaming 1080i video from my HDHomerun TV tuner

* I misinterpreted output from gcc diagnostics, and concluded that
  "march=-native" left several flags disabled that shouldn't be

* acting on that (mis)information), I emerged system+world+kernel and
  found that not only could my system handle 1080i, it could handle a
  1080p Youtube clip without problems, after a lot of buffering.  My 5
  megabit ADSL connection was the limiting factor there.  It's supposed
  to be upgraded to 6 megabits one of these days, for some minor
  improvement.

* I mistakenly thought that it was the additional flags in CFLAGS during
  the emerge system+world that boosted the video.  Actually, the emerge
  would've done the trick.

  The lesson from this is that, before doing any benchmarking or
heavy-duty usage, one should emerge system+world, to replace the generic
code from the install CD with fully optimized code.  It's easiest to so
right after the initial install, so that there are as few packages to
emerge as possible.

-- 
Walter Dnes <waltdnes@waltdnes.org>



  parent reply	other threads:[~2011-12-19  0:07 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-17 21:07 [gentoo-user] -march=native is *EXTREMELY* conservative Walter Dnes
2011-12-17 21:53 ` Dale
2011-12-17 21:58 ` [gentoo-user] " Nikos Chantziaras
2011-12-18  1:10   ` Walter Dnes
2011-12-18 10:34     ` Walter Dnes
2011-12-18 10:45       ` Nikos Chantziaras
2011-12-18 18:10         ` Andrea Conti
2011-12-19  0:05         ` Walter Dnes [this message]
2011-12-19  0:17           ` [gentoo-user] A tale of computing thud and blunder Dale
2011-12-19  5:41             ` Pandu Poluan
2011-12-19  6:15               ` Dale
2011-12-19  6:49                 ` [gentoo-user] " Nikos Chantziaras
2011-12-19  7:21                   ` Dale
2011-12-19 12:49                   ` walt
2011-12-19  8:14                 ` [gentoo-user] " Pandu Poluan
2011-12-19 16:37                 ` Paul Hartman
2011-12-18  1:15 ` [gentoo-user] -march=native is *EXTREMELY* conservative Paul Hartman

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=20111219000522.GA22397@waltdnes.org \
    --to=waltdnes@waltdnes.org \
    --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