From: Paulo Marques <pmarques@grupopie.com>
To: linux-kernel@vger.kernel.org
Subject: Performance disparity, problem found
Date: Thu, 01 Apr 2010 12:30:41 +0100 [thread overview]
Message-ID: <4BB483E1.9050203@grupopie.com> (raw)
Hi, all
I have two machines that show very different performance numbers.
After digging a little I found out that the first machine has, in
/proc/cpuinfo:
model name : Intel(R) Celeron(R) M processor 1.00GHz
while the other has:
model name : Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
and that seems to be the main difference.
Now the problem is that /proc/cpuinfo is read only. Would it be possible
to make /proc/cpuinfo writable so that I could do:
echo -n "model name : Intel(R) Core(TM)2 Quad CPU Q6600 @
2.40GHz" > /proc/cpuinfo
in the first machine and get a performance similar to the second machine?
--
Paulo Marques - www.grupopie.com
"To know recursion, you must first know recursion."
next reply other threads:[~2010-04-01 11:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-01 11:30 Paulo Marques [this message]
2010-04-01 12:30 ` Performance disparity, problem found Frans Pop
2010-04-01 13:50 ` Paulo Marques
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=4BB483E1.9050203@grupopie.com \
--to=pmarques@grupopie.com \
--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