From: shobhit dayal <shobhit@calsoftinc.com>
To: linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [RFC] [PATCH] Performance of del_single_shot_timer_sync
Date: Fri, 08 Oct 2004 19:07:39 +0530 [thread overview]
Message-ID: <1097242659.11717.483.camel@kuber> (raw)
Andrew Morton wrote:
> By how much? (CPU load, overall runtime, etc)
>
> It's a bit odd to have an expired-timer-intensive workload. Presumably
> postgres has some short-lived nanosleep or select-based polling loop in
> there which isn't doing much.
I am running this load on a numa hardware so I profile the kernel by logging
functions that cause remote node memory access. I generate a final log
that shows functions that cause remote memory accesses greater that 0.5%
of all remote memory access on the system.
del_timer_sync was responsible for about 2% of all remote memory
accesses on the system and came up as part of the top 10 functions who
were doing this. On top was schedule(7.52%) followed by
default_wake_function(2.79%). Rest every one in the top 10 were
around the range of 2%.
After the patch it never came up in the logs again( so less than 0.5% of
all faulting eip's).
regards
shobhit
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
>
>
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next reply other threads:[~2004-10-08 13:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-08 13:37 shobhit dayal [this message]
2004-10-08 17:19 ` [RFC] [PATCH] Performance of del_single_shot_timer_sync Andrew Morton
2004-10-10 10:29 ` shobhit dayal
-- strict thread matches above, loose matches on Subject: below --
2004-10-04 7:24 shobhit dayal
2004-10-04 8:41 ` Andrew Morton
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=1097242659.11717.483.camel@kuber \
--to=shobhit@calsoftinc.com \
--cc=akpm@osdl.org \
--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