2010/11/12 Yury Bushmelev <[email protected]>: >> I've collected some data about disk usage while doing last testing build. >> Here you can see it: http://bit.ly/dnzIrq >> Or long direct url: >> https://spreadsheets.google.com/ccc?key=0AhY8lmfkCabTdGZRSGZ0eXg5cWhkV2k1c0Jvd0lvVnc&authkey=CLeK150N#gid=0 > > I've added 'Chart 2' sheet to this document. > Direct link is > https://spreadsheets.google.com/ccc?key=0AhY8lmfkCabTdGZRSGZ0eXg5cWhkV2k1c0Jvd0lvVnc&authkey=CLeK150N#gid=1
New data again: https://spreadsheets.google.com/a/jay-tech.ru/ccc?key=0AhY8lmfkCabTdGZRSGZ0eXg5cWhkV2k1c0Jvd0lvVnc&authkey=CLeK150N#gid=2 https://spreadsheets.google.com/a/jay-tech.ru/ccc?key=0AhY8lmfkCabTdGZRSGZ0eXg5cWhkV2k1c0Jvd0lvVnc&authkey=CLeK150N#gid=3 First (Chart 3) is build with BB_SCHEDULER="completion" (default when using rm_work). Second (Chart 4) is build with BB_SCHEDULER="speed" (default when rm_work is not used). As you can see, "speed" scheduler slightly improved build time (about 40 min for me) but about 40Gb of disk peak space was used. "Completion" is a bit slower but uses about 34Gb in peak. -- Yury Bushmelev _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
