public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Gregg" <gregg@sc.am>
To: <arutha@gmx.de>
Cc: <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] Upgrade, course of action.
Date: Fri, 23 Aug 2002 15:45:25 -0500 (CDT)	[thread overview]
Message-ID: <1025.12.247.253.40.1030135525.squirrel@sc.am> (raw)
In-Reply-To: <200208232130.20064.arutha@gmx.de>

Lets say this is a learning experience.  I feel like learning to be brave
than learning to be behind (why I chose gentoo over debian.)  :)

Gregg

> On Friday 23 August 2002 11:22, Gregg wrote:
>> I run a server, it hosts 127 websites.  Has many users for various
>> other
>
> And you really host that on a gcc 3 system ? Brave :)
>
>> my flags in the configuration files.  So it is all just i686 in the
>> c*flags.  I want to go up to an athlon 2200.  So, what do I need to
>> consider before switching them out, what do I need to do afterword .
>> This is a 1.3b_test system with all the latest updates (except gcc
>> 3.2, I am still on 3.1.1)
>
> Just leave it "as is" and upgrade your hw. You can of course try to
> compile  your system with athlon optimizations afterwards but that's
> even more brave  than simply running a production system on gcc3 :)
>
> Btw. for servers more CPUs is better than one fast CPU. Think about it:
> One  fast CPU you have to serve 2 requests. One request gets the CPU for
> time x  then the sheduler decides that the second request gets cpu time
> and so forth  until both requests are served. With 2 CPUs both requests
> can be served in  parallel (really parallel not that pseudo parallelism
> the sheduler gets out  of your one cpu).
>
>
> Alex
>
> --
> "They that can give up essential liberty to obtain a little temporary
> safety  deserve neither liberty nor safety."
> Benjamin Franklin
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev





  reply	other threads:[~2002-08-23 20:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-23  9:22 [gentoo-dev] Upgrade, course of action Gregg
2002-08-23 16:30 ` [gentoo-dev] Re: [gentoo-user] " Michael Monsen
2002-08-23 16:31 ` Michael Monsen
2002-08-23 18:20   ` Dominik Westner
2002-08-23 19:30 ` [gentoo-dev] " Alexander Gretencord
2002-08-23 20:45   ` Gregg [this message]
2002-08-24  1:25 ` Charles Lacour
2002-08-24  5:24   ` Gregg
2002-08-24  6:41     ` [gentoo-dev] " Paul
2002-08-24  8:03     ` [gentoo-dev] " Thomas M. Beaudry
2002-08-24 11:59     ` Alexander Gretencord
2002-08-25  0:28       ` Gregg
2002-08-25  4:58       ` Thomas M. Beaudry

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=1025.12.247.253.40.1030135525.squirrel@sc.am \
    --to=gregg@sc.am \
    --cc=arutha@gmx.de \
    --cc=gentoo-dev@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