public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jvdelisle at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/56981] Slow I/O: Unformatted 5x slower, large sys component; formatted slow as well
Date: Sun, 08 Jun 2014 23:57:00 -0000 [thread overview]
Message-ID: <bug-56981-4-saQaAHbT1U@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56981-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56981
--- Comment #12 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
$ strace -c ./a.out
% time seconds usecs/call calls errors syscall
------ ----------- ----------- --------- --------- ----------------
99.97 0.078667 0 1000000 write
0.03 0.000022 2 11 fstat
0.00 0.000000 0 5 read
0.00 0.000000 0 17 10 open
0.00 0.000000 0 7 close
0.00 0.000000 0 8 6 stat
0.00 0.000000 0 17 mmap
0.00 0.000000 0 12 mprotect
0.00 0.000000 0 1 munmap
0.00 0.000000 0 3 brk
0.00 0.000000 0 10 rt_sigaction
0.00 0.000000 0 10 9 access
0.00 0.000000 0 1 execve
0.00 0.000000 0 1 readlink
0.00 0.000000 0 1 arch_prctl
------ ----------- ----------- --------- --------- ----------------
100.00 0.078689 1000104 25 total
This is looking pretty good now!
prev parent reply other threads:[~2014-06-08 23:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-56981-4@http.gcc.gnu.org/bugzilla/>
2013-04-16 15:20 ` burnus at gcc dot gnu.org
2013-04-17 0:58 ` jvdelisle at gcc dot gnu.org
2013-04-17 10:50 ` jb at gcc dot gnu.org
2013-04-17 14:50 ` burnus at gcc dot gnu.org
2013-04-18 1:21 ` jvdelisle at gcc dot gnu.org
2013-04-19 10:34 ` jb at gcc dot gnu.org
2013-04-29 9:35 ` burnus at gcc dot gnu.org
2013-04-29 9:36 ` burnus at gcc dot gnu.org
2013-12-21 20:15 ` dominiq at lps dot ens.fr
2014-06-08 18:08 ` jvdelisle at gcc dot gnu.org
2014-06-08 23:57 ` jvdelisle at gcc dot gnu.org [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=bug-56981-4-saQaAHbT1U@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).