512mb works fine, 1024mb RAM is slow...

From: Robin (robin_at_mhfm.cjb.net)
Date: 03/27/04 

Date: Sat, 27 Mar 2004 17:38:28 +0100

I have Redhat 9, on a p4 2,66. 1024 mb ram.
When I have 512 mb in it, it runs fine, no problems.
But when I put the other stick of 512 in it, it runs like 10 times slower,
Booting takes ages (about 5-10 minutes) and running a simple program will
use much more of the cpu then normal
'top' shows a load of 1,5% cpu usage, but with 512 mb ram it's just 0 %,
also when just booted uptime gives a load of 1.75.

How can this be possible? / How can I solve it?

Relevant Pages

  • 512mb works fine, 1024mb RAM is slow...
    ... Booting takes ages and running a simple program will ... use much more of the cpu then normal ... also when just booted uptime gives a load of 1.75. ...
    (alt.os.linux.redhat)
  • Re: Fwd: Re: New Metrics to measure Load average
    ... School of Electrical and Information Engineering ... Currently for the Phd, I am using division of load as per login users and this is what I want to have for HPC and for the "Task Profiling Model". ... Be very wary if their planned CPU controller as the model that they intend to use will only work with CPU bound processes. ...
    (Linux-Kernel)
  • Re: Cant get 5 volts at Firepower CPU
    ... of low voltage at the CPU? ... score, game settings, audit totals). ... the 4.9 volts at the CPU board EPROM pin 24. ... you're back to booting into audit ...
    (rec.games.pinball)
  • [PATCH 2/2] sched: Improve fairness of cpu allocation for task groups
    ... The current load balancing scheme isn't good for group fairness. ... Col4 -> CPU bandwidth received by each individual task of the group. ... Currently cpu's weight is just the summation of individual task weights. ...
    (Linux-Kernel)
  • [PATCH] sched: Consolidated and improved smpnice patch
    ... The introduction of separate run queues per CPU has brought with it "nice" enforcement problems that are best described by a simple example. ... whether this expectation is met is pretty much down to luck as there are four equally likely distributions of the tasks to the CPUs that the load balancing code will consider to be balanced with loads of 2.0 for each CPU. ... To overcome this problem SCHED_LOAD_SCALE has been replaced by the load_weight for the relevant task or by the average load_weight per task for the queue in question. ...
    (Linux-Kernel)