[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: New Computer



It is now pretty clear that my dual processor production machine is running
on one CPU.  It only got a few more stars processed than a slower machine
running the third pipeline.  This is consistent with running on one CPU. 
Sigh!  How do I get second processors turned on?  What could have made it
decide to turn off a processor?

Tom Droege


> [Original Message]
> From: Thomas Droege <tdroege2@earthlink.net>
> To: tass <tass@listserv.wwa.com>
> Date: 9/6/2003 1:02:08 PM
> Subject: New Computer
>
> I just got my new dual processor computer and fired it up.  I ran top and
> noticed that it did not show 2 CPUs.  This led me to look at my other dual
> processor computer and notice that it too shows only one processor, I
> recall that it used to show two.  Further, it shows each of the two
> pipeline jobs as using 50% of the CPU cycles.  I recall that it used to
> show near 100% for each of the two jobs.  
>
> I then went back and wrote a timing job for the new computer.  When I
> started a second job, the speed of both slowed down by a factor of two. 
> Further top shows both jobs running at 50%.   I thought with a two cpu
> system it should take 3 jobs before the first two started to slow. 
> (allowing for the system stuff)
>
> 1) How do I tell if they put two processors in the new box without opening
> it up?  I cannot find anyplace in the Linux config stuff where it lists
the
> CPUs.  The bios does not say anything about enabling the second CPU.
>
> 2)  I notice the memory in top is shown as somewhat less than 1 GByte.  I
> bought 2 Gbytes and 2 show up on the bios start screen. Should top show 2
> GBytes?
>
> 3)  Has something happened to my dual processor production machine?  It
> does seem to be going slower than I remember?  How can I test it while it
> is running the pipeline jobs?
>
> I never cease to be amazed that modern computer systems work as well as
> they do.  Still, I feel somewhat helpless when things like this happen.  
>
> Tom Droege
>
>
>
>
>