<html><body><div style="font-family: arial, helvetica, sans-serif; font-size: 12pt; color: #000000"><div><br></div><div><br></div><hr id="zwchr" data-marker="__DIVIDER__"><div data-marker="__HEADERS__"><blockquote style="border-left: 2px solid #1010FF; margin-left: 5px; padding-left: 5px; color: #000; font-weight: normal; font-style: normal; text-decoration: none; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;" data-mce-style="border-left: 2px solid #1010FF; margin-left: 5px; padding-left: 5px; color: #000; font-weight: normal; font-style: normal; text-decoration: none; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;"><b>From: </b>"Steve Litt" <slitt@troubleshooters.com><br><b>To: </b>ale@ale.org<br><b>Sent: </b>Tuesday, August 18, 2015 9:52:06 PM<br><b>Subject: </b>Re: [ale] Desktop 32GB of RAM<br></blockquote></div><div data-marker="__QUOTED_TEXT__"><blockquote style="border-left: 2px solid #1010FF; margin-left: 5px; padding-left: 5px; color: #000; font-weight: normal; font-style: normal; text-decoration: none; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;" data-mce-style="border-left: 2px solid #1010FF; margin-left: 5px; padding-left: 5px; color: #000; font-weight: normal; font-style: normal; text-decoration: none; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;">On Tue, 18 Aug 2015 20:36:19 -0400 (EDT)<br>Chris Fowler <cfowler@outpostsentinel.com> wrote:<br><br>> No VMs. Current desktop I built 01/2012. Needs faster disk I/O. I<br>> spend about 45 minutes waiting on a compile of software when I do a<br>> fresh checkout. <br>> <br>> The reason I said 64GB is because when I was pricing out a<br>> workstation on Penguin Computing's website the lowest was 64.<br>> Personally, 16 is fine. With 64 though I could copy the source tree<br>> into a ramdisk. Luckily I do have a UPS under my desk. :) <br><br>The ramdisk idea seems good, although 64GB seems kind of big for a<br>source tree (but a du -h would settle that matter).<br></blockquote><div><br></div><div>32GB would be the max. The tree is actually a SVN checkout within a CentOS 5.X tree. Hard to explain. I run Ubuntu on my desktop. In my home </div><div>directory I have ~/CentOS-5.3. I run a script as root that will mount /proc, /dev, /dev/pts, /sys, etc as bind within that directory. I then run 'chroot CentOS-5.3 program.pl' and the next thing I know I am now in that root and can do things as if I was on the real CentOS system. I've been using this method for MANY years. I even have a RH 8.0 tree we still maintain code on! My SOP for creating a new devroot like this is to use vmplayer to do an install of CentOS and then from my desktop I execute 'ssh root@vm "tar <options here> -cf -" | tar -xvf -'. Shutdown vmplayer and not boot it again. </div><div><br data-mce-bogus="1"></div><div>Since I'm building new many ideas come to mind. Use Xen? Have my desktop as one vm and then CentOS 7 as another? Can that CentOS's root be a ram disk? If so, how would I populate it? Maybe use rsync in its initrd image and then pivot_root? I can then have a nightly process that would rsync that root back to the real drive. Failure of that rsync can text my phone. UPS would be required.</div><div><br data-mce-bogus="1"></div><div>Many possibilities!</div></div></div></body></html>