From: Eric Piel <Eric.Piel@lifl.fr>
To: Sheo Shanker Prasad <ssp@creativeresearch.org>
Cc: "David S. Miller" <davem@davemloft.net>, linux-kernel@vger.kernel.org
Subject: Re: Disturbing wide variation in execution time
Date: Thu, 07 Jul 2005 11:53:37 +0200 [thread overview]
Message-ID: <42CCFBA1.1090807@lifl.fr> (raw)
In-Reply-To: <200507070103.25563.ssp@creativeresearch.org>
(please do not top-post)
07.07.2005 10:03, Sheo Shanker Prasad wrote/a écrit:
> Dear David,
>
> The program is an atmospheric chemistry-transport modeling code that computes
> the distributions of atmospheric species (e.g., ozone) as a function of
> latitude and altitude and how that changes with time.
Well, to let us examine your problem, you need to describe what
*technicaly* does your program. ie: lots of disk access, lots of
networks acces, lots of CPU access, allocate huge memory... in
particular, is it CPU bound or I/O bound? You should also mention how
tasks/thread is your program composed of.
It's good to describe your hardware: cluster of NUMA computers or just
one x86? How much memory, what kind of network, how many hard disks,
which exact version of the kernel....
Cherry on the top, you could include a *small* program which exhibit the
same problem.
>
> Thanks for taking time to think about my problem. I greatly appreciate it.
>
To answer briefly your question, _in general_ a program which takes more
than a few seconds to execute should take roughly the same time to
execute all the times.
Eric
next prev parent reply other threads:[~2005-07-07 9:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-07 6:44 Disturbing wide variation in execution time Sheo Shanker Prasad
2005-07-07 7:10 ` David S. Miller
2005-07-07 8:03 ` Sheo Shanker Prasad
2005-07-07 9:53 ` Eric Piel [this message]
2005-07-07 18:46 ` Philippe Troin
2005-07-08 21:51 ` Sheo Shanker Prasad
2005-07-08 0:41 ` michael
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=42CCFBA1.1090807@lifl.fr \
--to=eric.piel@lifl.fr \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=ssp@creativeresearch.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