From: Grant Coady <gcoady@gmail.com>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Bernd Eckenfels <be-news06@lina.inka.de>, linux-kernel@vger.kernel.org
Subject: Re: Why is 2.4.32 four times faster than 2.6.14.6??
Date: Mon, 09 Jan 2006 06:20:41 +1100 [thread overview]
Message-ID: <aap2s1diakl9dg7noa8a4p4kr688lhc1b5@4ax.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0601081303140.30148@yvahk01.tjqt.qr>
On Sun, 8 Jan 2006 13:04:22 +0100 (MET), Jan Engelhardt <jengelh@linux01.gwdg.de> wrote:
>
>>grant@deltree:~$ time grep -v 192\.168\. /var/log/apache/access_log |cut -c-96
>>
>>real 0m1.671s
>>user 0m0.550s
>>sys 0m0.300s
>>grant@deltree:~$ time grep -v 192\.168\. /var/log/apache/access_log |cut -c-96 >/dev/null
>>
>>real 0m0.510s
>>user 0m0.420s
>>sys 0m0.080s
>
>Given that the first command is the first one accessing access_log at
>all, then: the second time, access_log is already cached and
>therefore can be accessed faster.
I did repeat measurements to check for variation due to caching,
and that is not what is happening, we comparing going out over
ssh terminal to dumping output locally.
Grant.
next prev parent reply other threads:[~2006-01-08 19:20 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-08 6:16 Why is 2.4.32 four times faster than 2.6.14.6?? Grant Coady
2006-01-08 6:58 ` Markus Rechberger
2006-01-08 7:18 ` Bernd Eckenfels
2006-01-08 7:42 ` Grant Coady
2006-01-08 8:00 ` Bernd Eckenfels
2006-01-08 8:11 ` Con Kolivas
2006-01-08 9:12 ` Bernd Eckenfels
2006-01-08 12:04 ` Jan Engelhardt
2006-01-08 19:20 ` Grant Coady [this message]
2006-02-22 19:27 ` Enrico Weigelt
2006-02-22 23:17 ` Adrian Bunk
2006-01-08 7:28 ` Grant Coady
2006-01-08 9:57 ` Willy Tarreau
2006-01-08 10:23 ` Bernd Eckenfels
2006-01-08 10:54 ` Willy Tarreau
2006-01-08 11:09 ` Bernd Eckenfels
2006-01-08 11:16 ` Willy Tarreau
2006-01-08 11:18 ` Grant Coady
2006-01-09 2:37 ` Jesse Brandeburg
2006-01-09 2:46 ` Lee Revell
2006-01-09 2:59 ` Grant Coady
2006-01-09 6:56 ` Grant Coady
2006-01-08 11:05 ` Grant Coady
2006-01-08 18:21 ` Octavio Alvarez Piza
2006-01-08 19:27 ` Grant Coady
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=aap2s1diakl9dg7noa8a4p4kr688lhc1b5@4ax.com \
--to=gcoady@gmail.com \
--cc=be-news06@lina.inka.de \
--cc=jengelh@linux01.gwdg.de \
--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).