<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom"><title>Marcin Juszkiewicz - disk</title><link href="https://marcin.juszkiewicz.com.pl/" rel="alternate"/><link href="https://marcin.juszkiewicz.com.pl/tag/disk/feed/" rel="self"/><id>https://marcin.juszkiewicz.com.pl/</id><updated>2008-10-01T16:51:00+02:00</updated><entry><title>How much RAM/HDD is enough?</title><link href="https://marcin.juszkiewicz.com.pl/2008/10/01/how-much-ramhdd-is-enough/" rel="alternate"/><published>2008-10-01T16:51:00+02:00</published><updated>2008-10-01T16:51:00+02:00</updated><author><name>Marcin Juszkiewicz</name></author><id>tag:marcin.juszkiewicz.com.pl,2008-10-01:/2008/10/01/how-much-ramhdd-is-enough/</id><summary type="html">&lt;p&gt;During recent discussions we got into common developer problem &amp;#8212; there is no such thing as enough disk space&amp;#8230; Later it also expanded to &lt;span class="caps"&gt;RAM&lt;/span&gt;&amp;nbsp;size.&lt;/p&gt;
&lt;p&gt;My current desktop machine has 4GiB of memory and two hard disks with &lt;span class="caps"&gt;820GB&lt;/span&gt; (763GiB real) of total capacity. And I have only 90GiB of …&lt;/p&gt;</summary><content type="html">&lt;p&gt;During recent discussions we got into common developer problem &amp;#8212; there is no such thing as enough disk space&amp;#8230; Later it also expanded to &lt;span class="caps"&gt;RAM&lt;/span&gt;&amp;nbsp;size.&lt;/p&gt;
&lt;p&gt;My current desktop machine has 4GiB of memory and two hard disks with &lt;span class="caps"&gt;820GB&lt;/span&gt; (763GiB real) of total capacity. And I have only 90GiB of free space on them. So what took most of space? Usual suspects: Poky and OpenEmbedded builds&amp;nbsp;(&lt;code&gt;du -hs&lt;/code&gt; took one hour with &amp;#8220;160GiB used&amp;#8221;&amp;nbsp;result).&lt;/p&gt;
&lt;p&gt;Which get us back to the subject &amp;#8212; how much disk space is enough today for development? It depends on area &amp;#8212; some people will be fine with less then &lt;span class="caps"&gt;100GB&lt;/span&gt;, some not. Laptop which I will soon send back to Intel has only &lt;span class="caps"&gt;80GB&lt;/span&gt; hdd and this is really not enough for me for Poky development (if it has to be the only machine). I know that few persons started to look for &lt;span class="caps"&gt;320GB&lt;/span&gt; (or larger) disks for their laptops&amp;nbsp;;D&lt;/p&gt;
&lt;p&gt;&lt;span class="caps"&gt;OK&lt;/span&gt;, with &amp;#8220;rm_work&amp;#8221; class I was able to do Poky builds with few gigabytes of free space. But small hard drive forced me to forget about using VirtualBox for testing in other distributions then Debian &amp;#8216;sid&amp;#8217; (which I use on all machines).&amp;nbsp;Currently &lt;code&gt;~/.Virtualbox&lt;/code&gt; on my desktop uses about 70GiB as I have there Fedora 8, Fedora 9, Ubuntu 8.04 and few other distributions which I use for testing does Poky works under&amp;nbsp;them.&lt;/p&gt;
&lt;p&gt;Other thing is doing strange builds&amp;#8230; In past I did lot of them &amp;#8212; record one took 270GiB of space (and two weeks of building). And I do not like to be space limited when doing them (&amp;#8220;rm_work&amp;#8221; is not always good way). I still plan to make such big ones from time to time as they allow to check does everything works (and also show new bugs to&amp;nbsp;fix).&lt;/p&gt;
&lt;p&gt;But how much &lt;span class="caps"&gt;RAM&lt;/span&gt; is enough? My previous desktop had 2.1GiB &lt;span class="caps"&gt;RAM&lt;/span&gt;, laptop which I use for x86 builds has only 1GiB. Current desktop has 4GiB of &lt;span class="caps"&gt;DDR2&lt;/span&gt; (low price made it affordable) and for OpenEmbedded or Poky builds it is more then enough (as no one use BitBake from times when 512MiB ram was not enough to just parse metadata). My machine usually maxx at 2.5-3GiB of used memory during heavy builds. When it will be not enough&amp;#8230; I still have 2 slots for &lt;span class="caps"&gt;RAM&lt;/span&gt; free&amp;nbsp;:)&lt;/p&gt;
&lt;p&gt;How it is for other&amp;nbsp;people?&lt;/p&gt;</content><category term="disk"/><category term="laptop"/><category term="openembedded"/><category term="poky"/><category term="testing"/></entry><entry><title>Where does my disk space go?</title><link href="https://marcin.juszkiewicz.com.pl/2008/03/06/where-does-my-disk-space-go/" rel="alternate"/><published>2008-03-06T15:10:00+01:00</published><updated>2008-03-06T15:10:00+01:00</updated><author><name>Marcin Juszkiewicz</name></author><id>tag:marcin.juszkiewicz.com.pl,2008-03-06:/2008/03/06/where-does-my-disk-space-go/</id><summary type="html">&lt;p&gt;I have nearly 400 gigabytes storage in my desktop. Some people will tell that this is a lot, some that it is quite small size. But everybody agrees with one simple rule: &amp;#8220;there is no such thing as big enough&amp;nbsp;storage&amp;#8221;.&lt;/p&gt;
&lt;p&gt;From time to time I have situation when I …&lt;/p&gt;</summary><content type="html">&lt;p&gt;I have nearly 400 gigabytes storage in my desktop. Some people will tell that this is a lot, some that it is quite small size. But everybody agrees with one simple rule: &amp;#8220;there is no such thing as big enough&amp;nbsp;storage&amp;#8221;.&lt;/p&gt;
&lt;p&gt;From time to time I have situation when I lack space for my projects (which can take &lt;span class="caps"&gt;17GB&lt;/span&gt; in one run). In such moments there is one solution handy: removing not needed data. But how to check what takes most of&amp;nbsp;space?&lt;/p&gt;
&lt;p&gt;Some time ago I discovered &lt;a href="http://dev.yorhel.nl/ncdu/" title="NCurses Disk Usage"&gt;ncdu&lt;/a&gt; application. It offers simple interface with all required informations &amp;#8212; list of directories with space used (all sorted by size). User can walk through directory structure, remove not needed ones, recalculate directory use &amp;#8212; everything what is needed in such&amp;nbsp;tool.&lt;/p&gt;
&lt;p&gt;Few minutes later &lt;span class="caps"&gt;40GB&lt;/span&gt; from old builds recovered&amp;nbsp;;)&lt;/p&gt;</content><category term="disk"/><category term="useful tools"/></entry></feed>