From: "Sasi Péter" <Peter.Sasi@t-systems.co.hu>
To: <gcc@gcc.gnu.org>
Cc: <mplayer-dev-eng@mplayerhq.hu>
Subject: [GCC 3.x] Performance testing for QA
Date: Mon, 02 Sep 2002 06:12:00 -0000 [thread overview]
Message-ID: <71EE24368CCFB940A79BD7002F14D76014BC21@exchange.uns.t-systems.tss> (raw)
Dear GCC people,
Allow me the humble question to ask you if it would possible to employ a simple yet efficient testing method from real life as opposed to the SPEC* (artificial) test?
Specifically I was thinking of running a few encoding/decoding/manipulation runs with mplayer on sample multimedia streams.
Main reasons I could think of are:
- Easy to test: all you need (sources, sample files) is available free at www.mplayerhq.hu (for Linux(intel, alpha), Solaris, Irix, etc.)
- Important for masses: it is one of the most widely used free software in the area gaining probably the most momentum nowadays (amongst performace hungry software)
- There is a lot of space for improvements: even the 2.95 series perform better than the ongoing 3.x series, but if going for the long term Intel's compiler currently wins hands down
I know it is not a very scientific measurement, still it does apply to a lot of people, andd is a reason why a lot of people still stick to the older versions.
New features are really an important thing to have, still they should not make it instead of the good performance, but exploiting it.
Summarizing the above:
- Do you think such measurements are feasible/worth and can supply usable input for the development?
- Do you lack the interest, the resources, or what else?
- Ifyou are not interested, is there a reasoning behind that? (point me to RTFM if applicable)
- In case of positive answers do you think profiling, code analysis or what else could be the way to improve the current situation? (get 3.x to the perf. level of 2.95.x)
Please CC my personal address in your reply, since I am not subscribed to any of your mailing lists.
Thank you for your precious time.
Best regards,
Peter
-- Sasi Péter E-mail: peter.sasi@t-systems.co.hu
Sr. Systems Engineer Internet: <http://www.t-systems.co.hu/>
T-Systems Unisoftware Ltd. Phone: +36 (1) 456 54 13
Hungary Fax: +36 (1) 456 54 99
Postal address: H-1453 Budapest 92, Pf.28. Mobile: +36 (30) 280 34 31
Address: H-1097 Budapest, Könyves Kálmán krt. 12-14. 3.em., Lurdy-Ház
next reply other threads:[~2002-09-02 13:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-02 6:12 Sasi Péter [this message]
2002-09-02 14:08 ` Andreas Jaeger
2002-09-02 14:47 Robert Dewar
2002-09-02 15:42 ` Timothy J. Wood
2002-09-02 15:49 Robert Dewar
2002-09-03 10:32 ` Dale Johannesen
2002-09-03 11:17 ` Kevin Atkinson
2002-09-02 15:50 Robert Dewar
2002-09-03 13:25 Robert Dewar
2002-09-03 13:31 ` Daniel Jacobowitz
2002-09-03 14:28 ` Jan Hubicka
2002-09-03 13:36 Robert Dewar
2002-09-03 13:41 ` Kevin Atkinson
2002-09-03 13:55 Robert Dewar
2002-09-03 14:05 ` Kevin Atkinson
2002-09-03 14:12 ` Dale Johannesen
2002-09-03 13:56 Robert Dewar
2002-09-03 14:15 Robert Dewar
2002-09-03 14:25 Robert Dewar
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=71EE24368CCFB940A79BD7002F14D76014BC21@exchange.uns.t-systems.tss \
--to=peter.sasi@t-systems.co.hu \
--cc=gcc@gcc.gnu.org \
--cc=mplayer-dev-eng@mplayerhq.hu \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).