From: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>
To: John Richard Moser <nigelenki@comcast.net>, Andre Tomt <andre@tomt.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: printf() overhead
Date: Mon, 10 Jan 2005 20:33:14 +0200 [thread overview]
Message-ID: <200501102033.14028.vda@port.imtp.ilyichevsk.odessa.ua> (raw)
In-Reply-To: <41E19F21.20001@comcast.net>
On Sunday 09 January 2005 23:16, John Richard Moser wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
>
> Andre Tomt wrote:
> | John Richard Moser wrote:
> |
> |> 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?
> |
> |
> | The terminal is a major factor; gnome-terminal for example can be
> | *extremely* slow.
> |
>
> Is there a way to give the data to the terminal and let the program go
> while that happens? Or is there an execution path (i.e. terminal says
> "WTF NO") that can be missed that way?
Buffering is finite. strace output most likely overflow it.
Also while strace may finish already, you won't see it in gnome terminal
until entire strace stdout/stderr is drawn. You will wait anyway. :)
--
vda
next prev parent reply other threads:[~2005-01-10 18:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-09 19:25 printf() overhead John Richard Moser
2005-01-09 19:41 ` Andre Tomt
2005-01-09 21:16 ` John Richard Moser
2005-01-10 18:33 ` Denis Vlasenko [this message]
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=200501102033.14028.vda@port.imtp.ilyichevsk.odessa.ua \
--to=vda@port.imtp.ilyichevsk.odessa.ua \
--cc=andre@tomt.net \
--cc=linux-kernel@vger.kernel.org \
--cc=nigelenki@comcast.net \
/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).