The installing/replacing memory in sets is basically due to older [but not too much older] motherboards ran dual channel RAM [new Intel 2P and some 1P is Triple and AMD is Quad Channel] and you don't want to mix RAM with different specs in the same channel. Also, possibly the manufacturer figures if one module failed it's 'partner' is apt to go soon so just replace both instead of having two trouble tickets to deal with stretched over several weeks.<br>
<br><div class="gmail_quote">On Fri, Jun 17, 2011 at 12:24 PM, Michael B. Trausch <span dir="ltr"><<a href="mailto:mike@trausch.us">mike@trausch.us</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On 6/17/2011 12:11 PM, Scott Castaline wrote:<br>
> Sorry for replying to a reply, but to Mike, htop is showing 16<br>
> incidents of mysql, whereas top is only showing 1. Each incident is<br>
> using 1.0% of memory. I also noticed several incidents of kworker*<br>
> running of which (about 20) I don't remember the %Mem for each.<br>
</div>You're probably seeing all of MySQL's threads in htop. They together<br>
will still be using only 1% of the memory...<br>
<br>
kworker is a kernel thread, which has something to do with ACPI.<br>
<div><div></div><div class="h5"><br>
--- Mike<br>
_______________________________________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
<a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
See JOBS, ANNOUNCE and SCHOOLS lists at<br>
<a href="http://mail.ale.org/mailman/listinfo" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
</div></div></blockquote></div><br>