public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: paolo@gcc.gnu.org
To: daniel.lemire@nrc.gc.ca, gcc-bugs@gcc.gnu.org,
	gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org
Subject: Re: libstdc++/10672: Binary IO with fstream is slow in 3.2+ compared to gcc 2.96
Date: Sun, 18 May 2003 08:26:00 -0000	[thread overview]
Message-ID: <20030518082501.23776.qmail@sources.redhat.com> (raw)

Synopsis: Binary IO with fstream is slow in 3.2+ compared to gcc 2.96

State-Changed-From-To: open->feedback
State-Changed-By: paolo
State-Changed-When: Sun May 18 08:25:00 2003
State-Changed-Why:
    This is already fixed in mainline (future 3.4).
    On my P4-2400, 10^6 iterations, 5 consecutive runs:
    2.96-99 (NB: *not* an official FSF release):
    -------
    2.630u 4.970s 0:07.64 99.4%     0+0k 0+0io 136pf+0w
    2.660u 4.930s 0:07.62 99.6%     0+0k 0+0io 136pf+0w
    2.790u 5.120s 0:07.97 99.2%     0+0k 0+0io 136pf+0w
    2.720u 4.840s 0:07.59 99.6%     0+0k 0+0io 136pf+0w
    2.830u 4.670s 0:07.54 99.4%     0+0k 0+0io 136pf+0w
    
    3.4 20030516
    ------------
    2.500u 4.790s 0:07.34 99.3%     0+0k 0+0io 217pf+0w
    2.570u 4.690s 0:07.31 99.3%     0+0k 0+0io 217pf+0w
    2.350u 4.990s 0:07.38 99.4%     0+0k 0+0io 217pf+0w
    2.650u 4.670s 0:07.38 99.1%     0+0k 0+0io 217pf+0w
    2.590u 4.720s 0:07.35 99.4%     0+0k 0+0io 217pf+0w
    
    Could you please provide one of those nasty testcases
    which were showing a 5x performance regression?
    
    Thanks for your report, Paolo.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10672


             reply	other threads:[~2003-05-18  8:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-18  8:26 paolo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-08  0:46 daniel.lemire

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=20030518082501.23776.qmail@sources.redhat.com \
    --to=paolo@gcc.gnu.org \
    --cc=daniel.lemire@nrc.gc.ca \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).