public inbox for gentoo-performance@lists.gentoo.org
 help / color / mirror / Atom feed
From: Joel Merrick <joel@joelmerrick.com>
To: gentoo-performance@lists.gentoo.org
Subject: Re: [gentoo-performance] Gentoo-performance forum?
Date: Tue, 12 Oct 2004 14:24:08 +0100	[thread overview]
Message-ID: <416BDAF8.80207@joelmerrick.com> (raw)
In-Reply-To: <921ad39e04101205471d902724@mail.gmail.com>

Roman Gaufman wrote:

>There is certainly potential here, but let me list why your method
>will be flawed:
>
>1) Non single user mode means you cant predict what deamon is doing
>what at what time.
>  
>

Damn, I knew there was something I missed ;)

>2) CFLAGS in make.conf are usually changed by users often. You need to
>test against the age of /var/log/emerge.log and test against the
>ebuild. Many ebuilds filter out several CFLAGS.
>  
>

Sure, I understand.. hopefully they would be the same across the board, 
so that would induce a kind of consistent baseline, however I'm sure 
they differ across ebuilds of the same software

>3) There's too many entries to fill in, prone to user error, false
>assumptions and ofcourse the people that will just fill in junk for
>the sake of it.
>  
>
Yea, good point again.. it's not supposed to be a be-all-and-end-all, 
just more of a (very limited) point of reference.. all the same notes 
above apply to the forums I suppose.. just depends what people take at 
face value

>I think a much better solution is to make a script that will auto
>reboot into single user mode, perform all tests, reboot into mult user
>mode and upload results.
>  
>
I agree!

>I could help write some of those tests and benchmarks.
>  
>
Cool! It'd be great to have standardisation... everyone singing from the 
same benchmark script ;)

Save them to XML and fire them up to a db for everyone to assess.

>I've worked on something similar earlier this year, but its really
>quite a major, complicated task thats a lot harder to achieve than
>just making a simple php page where people fill in values.
>
>Thats why I suggested a performance forum, so things can be discussed
>and polished before a good quality, comprehensive database can be
>made.
>  
>
Yea, don't get me wrong I agree wholey with you, was just thinking about 
interim solutions as I'm sure to setup the scripts et al. would be a 
big, time consuming job!

>
>On Tue, 12 Oct 2004 12:45:27 +0100, Joel Merrick <joel@joelmerrick.com> wrote:
>  
>
SNIP 8<

--
gentoo-performance@gentoo.org mailing list


      reply	other threads:[~2004-10-12 13:24 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-09 18:03 [gentoo-performance] Gentoo-performance forum? Roman Gaufman
2004-10-09 19:36 ` Spoiala Cristian
2004-10-11  8:36 ` M. Steffan Noé
2004-10-11  9:49   ` Roman Gaufman
2004-10-11 10:06     ` Antoine Raillon
2004-10-11 10:48       ` Tarax
2004-10-11 12:22         ` Roman Gaufman
2004-10-11 12:35           ` Joel Merrick
2004-10-11 12:43             ` Roman Gaufman
2004-10-11 12:44               ` Thomas Lasswell
2004-10-11 13:02               ` Joel Merrick
2004-10-11 13:15                 ` Roman Gaufman
2004-10-11 15:47 ` Lance Albertson
2004-10-11 16:31   ` Roman Gaufman
2004-10-12 10:39   ` Joel Merrick
2004-10-12 10:53     ` Daniel Armyr
2004-10-12 11:45       ` Joel Merrick
2004-10-12 12:47         ` Roman Gaufman
2004-10-12 13:24           ` Joel Merrick [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=416BDAF8.80207@joelmerrick.com \
    --to=joel@joelmerrick.com \
    --cc=gentoo-performance@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