From: John Richard Moser <nigelenki@comcast.net>
To: linux-kernel@vger.kernel.org
Subject: printf() overhead
Date: Sun, 09 Jan 2005 14:25:22 -0500 [thread overview]
Message-ID: <41E18522.7060004@comcast.net> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
using strace to run a program takes aeons. Redirecting the output to a
file can be a hundred times faster sometimes. This raises question.
I understand that output to the screen is I/O. What exactly causes it
to be slow, and is there a possible way to accelerate the process?
- --
All content of all messages exchanged herein are left in the
Public Domain, unless otherwise explicitly stated.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFB4YUhhDd4aOud5P8RAonuAJ0ejEn1+oaiZnJIAGp2kFUyd8pgSwCdFaco
JgKsWYZfEcemGO3mZvL+KZY=
=vWqA
-----END PGP SIGNATURE-----
next reply other threads:[~2005-01-09 19:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-09 19:25 John Richard Moser [this message]
2005-01-09 19:41 ` printf() overhead Andre Tomt
2005-01-09 21:16 ` John Richard Moser
2005-01-10 18:33 ` Denis Vlasenko
2005-01-09 20:27 ` Gene Heskett
[not found] <no.id>
2005-01-09 21:24 ` Alan Curry
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=41E18522.7060004@comcast.net \
--to=nigelenki@comcast.net \
--cc=linux-kernel@vger.kernel.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 NNTP newsgroup(s).