All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@osdl.org>
To: Ulrich Drepper <drepper@redhat.com>
Cc: "Bill Rugolsky Jr." <brugolsky@telemetry-investments.com>,
	Paul Venezia <pvenezia@jpj.net>,
	Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: ext3 performance inconsistencies, 2.4/2.6
Date: Tue, 4 Nov 2003 14:31:18 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.44.0311041422580.20373-100000@home.osdl.org> (raw)
In-Reply-To: <3FA82161.9000507@redhat.com>


On Tue, 4 Nov 2003, Ulrich Drepper wrote:
> 
> I don't see any verison numbers mentioned.  If you want to benchmark
> NPTL use the recent code, e.g., from Fedora Core 1 or RHEL3.  Nothing
> else makes any sense since there have mean countless changes since the
> early releases.

This is actually _really_ trivial to see with a simple test program.

This is Fedora Core test3:

	#include <stdlib.h>

	/* Change this to match your CPU */
	#define NR (10*1000*1000)

	int main(int argc, char **argv)
	{
	        int i;
	        for (i = 0; i < NR; i++)
	                putchar(0);
	}

and then just time it.

I get:

	torvalds@home:~> time ./a.out > /dev/null 

	real    0m1.305s
	user    0m1.283s
	sys     0m0.004s

and

	torvalds@home:~> time LD_ASSUME_KERNEL=2.4.1 ./a.out > /dev/null 
	
	real    0m0.321s
	user    0m0.318s
	sys     0m0.003s

ie a factor of _four_ difference in the speed of "putchar()".

Interestingly, if I compile the program statically, I don't see this 
effect, and it's noticeably faster still:

	torvalds@home:~> gcc -O2 -static test.c 
	torvalds@home:~> time ./a.out > /dev/null 

	real    0m0.193s
	user    0m0.191s
	sys     0m0.002s

	torvalds@home:~> time LD_ASSUME_KERNEL=2.4.1 ./a.out > /dev/null 

	real    0m0.194s
	user    0m0.190s
	sys     0m0.004s

Is the TLS stuff done through an extra dynamically loaded indirection or
something?

		Linus


  reply	other threads:[~2003-11-04 22:31 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-04 19:10 ext3 performance inconsistencies, 2.4/2.6 Paul Venezia
2003-11-04 19:36 ` Linus Torvalds
2003-11-04 20:20   ` Bill Rugolsky Jr.
2003-11-04 20:30     ` Linus Torvalds
2003-11-04 21:07       ` Paul Venezia
2003-11-04 21:28         ` Bill Rugolsky Jr.
2003-11-04 21:40           ` Linus Torvalds
2003-11-04 22:00             ` Ulrich Drepper
2003-11-04 22:31               ` Linus Torvalds [this message]
2003-11-04 23:48                 ` Ulrich Drepper
2003-11-04 23:56                   ` Linus Torvalds
2003-11-05  0:58                   ` jlnance
2003-11-05  7:08                     ` Jakub Jelinek
2003-11-04 22:19             ` Bill Rugolsky Jr.
2003-11-04 22:26               ` Bill Rugolsky Jr.
2003-11-05  7:14               ` Jakub Jelinek
2003-11-04 21:39       ` Bill Rugolsky Jr.

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=Pine.LNX.4.44.0311041422580.20373-100000@home.osdl.org \
    --to=torvalds@osdl.org \
    --cc=brugolsky@telemetry-investments.com \
    --cc=drepper@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pvenezia@jpj.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.