From: michael@optusnet.com.au
To: Sheo Shanker Prasad <ssp@creativeresearch.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Disturbing wide variation in execution time
Date: 08 Jul 2005 10:41:54 +1000 [thread overview]
Message-ID: <m2fyuqt9gt.fsf@mo.optusnet.com.au> (raw)
In-Reply-To: <200507062344.53615.ssp@creativeresearch.org>
Sheo Shanker Prasad <ssp@creativeresearch.org> writes:
[...]
> When the repaired machine was started, I began to notice the disturbing wide
> variation and the frequect significant slow down of the machine as exhibited
> by the factor of 2 to 2.5 increased execution time of the test program as
> described above. Sometimes it would be quite fast (executing at the original
> 2m 40s) and sometime a factor of 2.5 slow, and sometimes with speed in
> between.
Something stuffed on the CPU heatsink causing thermal speed throttling?
Just a wild guess.
Michael.
prev parent reply other threads:[~2005-07-08 0:41 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
2005-07-07 18:46 ` Philippe Troin
2005-07-08 21:51 ` Sheo Shanker Prasad
2005-07-08 0:41 ` michael [this message]
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=m2fyuqt9gt.fsf@mo.optusnet.com.au \
--to=michael@optusnet.com.au \
--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 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.