public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Adam Porich <adam@burrabooks.com>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] "Distro Day (Measuring the benefits of the Gentoo approach)"
Date: Thu, 14 Aug 2003 03:46:55 +1000	[thread overview]
Message-ID: <20030814034655.37b290e0.adam@burrabooks.com> (raw)
In-Reply-To: <1060781901.7508.17.camel@biproc>

On 13 Aug 2003 15:38:21 +0200
Philippe Lafoucrière <lafou@wanadoo.fr> wrote:

> here is an article comparing debian / mandrake / gentoo speed :
> 
> http://articles.linmagau.org/modules.php?op=modload&name=Sections&file=index&req=viewarticle&artid=227&page=1http://articles.linmagau.org/modules.php?op=modload&name=Sections&file=index&req=viewarticle&artid=227&page=1
> 

I'm sorry to mention this again but the speed of a distribution is more than what benchmarks can show, I have seen a few benchmarks come out in the past few days that say that gentoo performace is less than satisfactory. But, I can say that having used my gentoo desktop for some time, and having used many others. I consider my gentoo desktop to be much faster and more responsive than others. The point is how fast a desktop is, is often a personal measure and not an easily quantifiable measure.

P.S. The init scripts and other built-in scripts are so much better that I don't care about performace under gentoo anyway.


--
gentoo-dev@gentoo.org mailing list


      parent reply	other threads:[~2003-08-13 17:46 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-13 13:38 [gentoo-dev] "Distro Day (Measuring the benefits of the Gentoo approach)" Philippe Lafoucrière
2003-08-13 14:07 ` brett holcomb
2003-08-13 15:03   ` Sven Vermeulen
2003-08-13 16:15     ` Alan
2003-08-13 20:30       ` Chris Gianelloni
2003-08-13 14:08 ` Chris Gianelloni
2003-08-13 14:12   ` Brad Laue
2003-08-13 14:20   ` Philippe Lafoucrière
2003-08-13 14:25     ` Philippe Lafoucrière
2003-08-13 14:32     ` Chris Gianelloni
2003-08-13 16:17       ` Alan
2003-08-13 16:22         ` Patrick Kursawe
2003-08-13 20:35           ` Chris Gianelloni
2003-08-13 20:32         ` Chris Gianelloni
2003-08-14 10:02           ` Paul de Vrieze
2003-08-13 21:15     ` FRLinux
2003-08-13 22:49       ` William Kenworthy
2003-08-14  2:04         ` Brian Jackson
2003-08-14 10:10         ` Paul de Vrieze
2003-08-14 12:30         ` Chris Gianelloni
2003-08-14 16:59           ` William Kenworthy
2003-08-14 17:38             ` [gentoo-dev] "Distro Day (Measuring the benefits of the Gentooapproach)" matt c
2003-08-14 19:22         ` [gentoo-dev] "Distro Day (Measuring the benefits of the Gentoo approach)" FRLinux
2003-08-14 23:01           ` William Kenworthy
2003-08-13 14:24 ` David Holm
2003-08-13 14:28   ` Philippe Lafoucrière
2003-08-13 16:16     ` Eric Olinger
2003-08-13 19:00   ` Jon Portnoy
2003-08-13 20:02     ` Mike Frysinger
2003-08-14  1:07       ` [gentoo-dev] 'Distro Day (Measuring the benefits of the Gentoo approach)' donnie berkholz
2003-08-14  1:13         ` Jon Portnoy
2003-08-14 11:01         ` Chris Gianelloni
2003-08-13 14:34 ` [gentoo-dev] "Distro Day (Measuring the benefits of the Gentoo approach)" Stuart Herbert
2003-08-13 14:34 ` Svyatogor
2003-08-13 17:46 ` Adam Porich [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=20030814034655.37b290e0.adam@burrabooks.com \
    --to=adam@burrabooks.com \
    --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