public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64]  Re: MAKEOPTS values for Athlon 64 X2
Date: Tue, 16 Jan 2007 11:11:42 +0000 (UTC)	[thread overview]
Message-ID: <eoibte$ro1$3@sea.gmane.org> (raw)
In-Reply-To: 45AC0F0A.5050408@digital-trauma.de

Thomas Rösner <Thomas.Roesner@digital-trauma.de> posted
45AC0F0A.5050408@digital-trauma.de, excerpted below, on  Tue, 16 Jan 2007
00:32:26 +0100:

> Duncan wrote:
>> As for disk access, the average guy with a single hard drive will
>> certainly find that the bottleneck in an unlimited jobs scenario such as
>> the above.  I'm running a four disk SATA based RAID array, RAID-6 (so
>> two-way-striped, with two-way recovery as well) on my main system,
> 
> Uhm, if you'd use RAID-1-1, you wouldn't have to calculate those
> checksums...

True, but computing checksums is relatively trivial compared to the I/O
overhead, and reading (which doesn't need checksums unless the
RAID array is operating in degraded mode) would be half-speed relative to a
4-disk RAID-6 (so two-way data striped). Given the trivial checksumming,
Writing would be comparable to a three-disk RAID-1, and is slower than a
two-disk RAID-1, as for every data stripe there's two parity stripes to
update, but there's not a lot of data actually written anyway during
emerges, since all the work is done on tmpfs and only the final write is
to the disk.  When compiling the kernel, I'm working directly on disk but
that mount is a four-way striped RAID-0, so I get its speed and no
checksumming overhead there.  (/boot is RAID-1 so GRUB can read it, so
when the kernel is actually installed, it's written to 4-way RAID-1, but
that's only one writing the completed kernel, so no big deal there.)

If I was running less than four disks, the choice would be a bit tougher,
between a 3-disk RAID-5 with two-way striped read speed but
two-way-mirrored (plus checksumming) write speed, while losing the
ability to recover from a two-drive failure, a 3-disk RAID-1, keeping the
two-drive recovery but at a severe cost in speed, or a 2-disk
RAID-1/mirrored. In that instance I expect the 2-disk RAID-1/mirrored
would win as it would be too difficult to justify either of the 3-disk
options.

> Btw, may I come to your place when UT2007 is out? ;-)

As a gamer, you'd probably not appreciate my choice of video card -- an
older but freedomware driver Radeon 9250.  I won't do
proprietaryware/slaveryware.

Luckily I'm not much of a gamer, but the rest of the hardware specs are
complimented by dual 400x300 mm (21" diag) monitors, normally running @
1600x1200 stacked for 1600x2400. I used to run 2048x1536 stacked for
2048x3072, but while it worked, text was blurry as that was below the
monitors' native pixel pitch (set for 1600x1200), and the 85 Hz refresh
doesn't hurt (I was limited to 60 Hz with the higher resolution,
acceptable with the light text on dark backgrounds I prefer, but not
ideal, or even tolerable with dark text on light backgrouns) either, so I
finally caved in and downgraded my resolution.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
gentoo-amd64@gentoo.org mailing list



      parent reply	other threads:[~2007-01-16 11:13 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-15  5:42 [gentoo-amd64] MAKEOPTS values for Athlon 64 X2 PaulNM
2007-01-15  9:17 ` Toshinori Endo
2007-01-15 15:39 ` Thomas Rösner
2007-01-15 18:10   ` [gentoo-amd64] " Duncan
2007-01-15 23:32     ` Thomas Rösner
2007-01-16  8:28       ` Andrei Slavoiu
2007-01-16 10:27         ` Neil Bothwick
2007-01-16 16:15           ` Peter Humphrey
2007-01-17  2:41         ` Thomas Rösner
2007-01-17  7:47           ` Duncan
2007-01-17 12:34             ` Boyd Stephen Smith Jr.
2007-01-17 17:24             ` Hemmann, Volker Armin
2007-01-17 19:02               ` Bernhard Auzinger
2007-01-17 21:22                 ` Hemmann, Volker Armin
2007-01-18  4:50                   ` Duncan
2007-01-18 16:12                     ` Hemmann, Volker Armin
2007-01-18 16:16                       ` Rob Lesslie
2007-01-18 18:10                         ` Boyd Stephen Smith Jr.
2007-01-18 18:35                           ` Simon Stelling
2007-01-18 19:13                             ` Boyd Stephen Smith Jr.
2007-01-18 19:51                               ` Simon Stelling
2007-01-26  8:49                             ` Peter Humphrey
2007-01-26 23:18                               ` Thomas Rösner
2007-01-18 18:41                       ` Duncan
2007-01-18 18:51                         ` Hemmann, Volker Armin
2007-01-18 19:17                           ` Duncan
2007-01-18 19:36                     ` Bob Young
2007-01-18 19:42                       ` Harry Holt
2007-01-19  7:57                         ` Duncan
2007-01-26  0:46                     ` Peter Humphrey
2007-01-16 11:11       ` Duncan [this message]

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='eoibte$ro1$3@sea.gmane.org' \
    --to=1i5t5.duncan@cox.net \
    --cc=gentoo-amd64@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