Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!cbatt!cbosgd!ihnp4!inuxc!pur-ee!uiucdcs!uiucdcsb!wsmith
From: wsmith@uiucdcsb.CS.UIUC.EDU
Newsgroups: net.unix
Subject: why is fprintf(stderr,) slow?
Message-ID: <19300053@uiucdcsb>
Date: Sun, 17-Aug-86 22:09:00 EDT
Article-I.D.: uiucdcsb.19300053
Posted: Sun Aug 17 22:09:00 1986
Date-Received: Tue, 19-Aug-86 04:36:33 EDT
Lines: 14
Nf-ID: #N:uiucdcsb:19300053:000:474
Nf-From: uiucdcsb.CS.UIUC.EDU!wsmith    Aug 17 21:09:00 1986


I was doing some performance testing on a program and as part of it
I was doing about 500 fprintf(stderr, "blah...\n");

The program was taking 35 or 40 seconds of system time which was pretty
high.  I then commented out the fprintf's and the program took 17 or 18
system time seconds (it was doing a lot of disk accesses).

Is this well known behavior that fprintf(stderr, ... ) takes a lot of time?
Why does it do so?

Bill Smith
ihnp4!uiucdcs!wsmith
wsmith@b.cs.uiuc.edu