My only concern was that there seems to be some emphasis on sets and that RMA required returning complete sets. I was thinking of getting just one stick of the same exact one for replaceing the bad one (Brand/Model) rather than getting another set of 4 sticks so that I'm not down waiting for the replacement. I understand that I need to match CAS/RAS specs and that was my intent. I just had the impression that mfg required you to get complete sets instead of buying individual sticks. I may be just picking up on marketing ploy and not really technical truths. <br>
<br>
<div class="gmail_quote">On Fri, Jun 17, 2011 at 9:09 AM, Greg Clifton <span dir="ltr"><<a href="mailto:gccfof5@gmail.com">gccfof5@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">I agree with Mike on the RAM. The important thing is to match the spec as closely as possible, not just the clock speed but CAS/RAS. If your bad RAM is branded, you should be able to go to the manufacturer's web site and get the specs. It is also possible that it is lifetime guaranteed RAM so you could get it replaced free. Other than that, most any brand is fine, the're all darned good these days.
<div>GC.
<div>
<div></div>
<div class="h5"><br>
<div><br></div>
<div><br>
<div class="gmail_quote">On Fri, Jun 17, 2011 at 7:58 AM, Scott Castaline <span dir="ltr"><<a href="mailto:skotchman@gmail.com" target="_blank">skotchman@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div>
<div></div>
<div><br><br>
<div class="gmail_quote">On Thu, Jun 16, 2011 at 10:08 PM, Michael B. Trausch <span dir="ltr"><<a href="mailto:mike@trausch.us" target="_blank">mike@trausch.us</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div>On 6/16/2011 8:01 PM, Scott Castaline wrote:<br>> 1. Just had 1 stick 2GB of RAM go bad. I had originally bought as part<br>> of a set of 4 sticks for a total of 8GB. My question is how critical<br>> is it to buy in matched sets? Couldn't I buy just a replacement for<br>
> that stick? I don't overclock so I don't push them so I can't see<br>> where I have to have handpicked memory. I would plan on getting the<br>> same exact mfg part on a single stick basis.Am I wrong tinking this way?<br>
<br></div>You should be fine ordering the part separately. The only thing that you<br>need to be sure of is that you match the specs of the memory that is in<br>the system currently.<br>
<div><br>> 2. I am currently running dd if=/dev/urandom of=/dev/sde on a new 2TB<br>> drive. I was logged into my GUI desktop (KDE) and after several hours<br>> my desktop started disintegrating and window apps were becoming<br>
> unrecognisable, but I was able to close ot most of them. I switched<br>> over to one of the text VTs and top was reporting that out of 4GB of<br>> RAM I only had less than 500MB available and I was starting to use<br>
> swap. I've done this in the past with only 4GB of RAM on different<br>> hardware and earlier version of Fedora, without any problems like<br>> this. I'm not doing anything that different than in the past. My<br>
> question is, what command(s) would tell me what is actually hogging<br>> all of the RAM? I don't want to kill the process as I'm anticipating<br>> it aking about 4 days to complete. At least on a 2 core AMD it toke<br>
> about 44 hours for 1TB, I'm not sure how much quicker a 4 core<br>> processor will do this. I was also running 800MHz RAM then, now I'm<br>> running 1333MHz RAM of course I realize that that is not the real<br>
> speed of the bus clock.<br><br></div>The 'dd' process is not going to run (significantly) differently on a<br>multicore/multiprocessor system than on a unicore/uniprocessor system;<br>nor would it likely if it were written to be a multithreaded program.<br>
The reason is that bandwidth limitations are going to be the bottleneck<br>of the command. Even on a system that can generate pseudorandom bytes<br>more quickly, the hard disk drives are going to be the limiting factor.<br>
<br>In order to find out which process is hogging memory, I'd recommend<br>"htop". Be sure to sort the output by the MEM% column.<br><br> --- Mike<br>_______________________________________________<br>Ale mailing list<br>
<a href="mailto:Ale@ale.org" target="_blank">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></blockquote></div></div></div>
<div><br>Will htop give me much different results than top? I found on top sorting by %mem that mysqld was at 1.0 which in my opinion is not a hog, but I'm not sure why it is there as I didn't install mysql unless some other app usees it. Also is it possible that it's not just a process but several processes used to do a certain task. I have noticed several proceses named khelper? where the ? is a different number for each one and there were others like that. I don't remember seeing these in earlier versions of Fedora.</div>
<div> </div>
<div>Also any recommendations on memory brands/model?</div><br>_______________________________________________<br>Ale mailing list<br><a href="mailto:Ale@ale.org" target="_blank">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><br></blockquote></div><br></div></div></div></div><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><br></blockquote></div><br>