| 1 |
<html> |
| 2 |
<head><title>scenarios where distcc can help</title> |
| 3 |
<meta name="author" content="Martin Pool"> |
| 4 |
<meta name="keywords" content="distributed, make, build, gcc, |
| 5 |
parallel, network, networked, faster, free, fast, paralel, cc, c, |
| 6 |
C++, Objective C, ObjC, compile, compiler, compilation, |
| 7 |
simple, GPL, GNU, Linux, BSD, Unix, software, development, |
| 8 |
developer, TeamBuilder, quick, dmake, pvmake, |
| 9 |
transparent, easy, workstations, Solaris, IncrediBuild, |
| 10 |
productivity, speed, time, tool, performance, hardware, |
| 11 |
agents, nfs, libraries, source, headers, workload, |
| 12 |
buildfarm, farm, server, cluster, clustered, clustering, MOSIX, OpenMOSIX"> |
| 13 |
<meta name="description" content="distcc is a fast, free distributed C and C++ compiler."> |
| 14 |
<link rel="SHORTCUT ICON" href="favicon.ico"> |
| 15 |
<link type="text/css" rel="stylesheet" href="distcc-green.css"> |
| 16 |
<link type="text/html" rel="top" href="index.html"> |
| 17 |
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"></head> |
| 18 |
<body vlink="#003300" text="#000000" link="#003300" bgcolor="#ffffff" alink="#336633"><p><table width="100%"><tr><td valign="top"><div class="navbar"><ul> |
| 19 |
<li><a href="index.html">distcc</a></li> |
| 20 |
<li><a href="http://code.google.com/p/distcc/source/browse/trunk">source</a> |
| 21 |
<li><a href="http://code.google.com/p/distcc/downloads/list">binaries</a></li> |
| 22 |
<li><a href="http://distcc.googlecode.com/svn/trunk/NEWS">news</a></li> |
| 23 |
<li><a href="scenarios.html"><b>scenarios</b></a></li> |
| 24 |
<li><a href="results.html">testimonials</a></li> |
| 25 |
<li><a href="benchmark.html">benchmarks</a></li> |
| 26 |
<li><a href="security.html">security</a></li> |
| 27 |
<li><a href="distcc-lca-2004.html">whitepaper</a></li> |
| 28 |
<li><a href="http://distcc.googlecode.com/svn/trunk/doc/web/man/">Man pages</a></li> |
| 29 |
<li><a href="faq.html">FAQ</a></li> |
| 30 |
|
| 31 |
<p> |
| 32 |
<li><a href="http://code.google.com/p/distcc/issues/list">report a bug</a></li> |
| 33 |
<li><a href="https://lists.samba.org/mailman/listinfo/distcc">mailing list</a> |
| 34 |
<ul><li><a href="mailto:[email protected]">post</a></li> |
| 35 |
<li><a href="http://lists.samba.org/archive/distcc/">archive</a></li> |
| 36 |
<li><a href="news://news.gmane.org/gmane.comp.compilers.distcc">newsgroup</a></li></ul> |
| 37 |
</li> |
| 38 |
<li><a href="http://freshmeat.net/projects/distcc">Freshmeat</a> |
| 39 |
<ul><li><a href="http://freshmeat.net/subscribe/28140">be notified</a></li></ul> |
| 40 |
</li> |
| 41 |
|
| 42 |
<p> |
| 43 |
<li>related:</li> |
| 44 |
<ul> |
| 45 |
<li><a title="How to use distcc and Gentoo" href="http://www.gentoo.org/doc/en/distcc.xml">Gentoo</a></li> |
| 46 |
<li><a title="Script to ease building cross-compilers and toolchains" href="http://kegel.com/crosstool/">crosstool</a></li> |
| 47 |
<li><a title="Cache compiler results" href="https://ccache.dev/">ccache</a></li> |
| 48 |
<li><a title="Centralized control over distcc and ccache" href="http://ccontrol.ozlabs.org/">ccontrol</a></li> |
| 49 |
<li><a title="Smart job scheduler" href="http://dmucs.sourceforge.net/">dmucs</a></li> |
| 50 |
</ul> |
| 51 |
<p><p></td> |
| 52 |
<td valign="top"> |
| 53 |
<div class="body"> |
| 54 |
<h1 class="title">scenarios where distcc can help</h1> |
| 55 |
|
| 56 |
<p> |
| 57 |
You don't need an enormous custom-built cluster to find distcc |
| 58 |
useful. Here are some typical scenarios where spending a little |
| 59 |
while installing distcc can pay off in improved productivity. |
| 60 |
|
| 61 |
<h2>workgroup of developers</h2> |
| 62 |
<p> |
| 63 |
You work in an office with several other people, each of whom has a |
| 64 |
PC, workstation or desktop. Perhaps you work on the same project, |
| 65 |
or perhaps on different projects. |
| 66 |
<p> |
| 67 |
Your project is moderately large, so it takes a while to build: |
| 68 |
waiting for it disrupts your concentration and makes development |
| 69 |
less fun. You waste time needing to rebuild when somebody changes a |
| 70 |
top-level header. |
| 71 |
<p> |
| 72 |
The solution is straightforward: run distcc on other |
| 73 |
machines, and make sure they have the compiler installed. Your |
| 74 |
machine can distribute work onto others, with lowered priority to |
| 75 |
make sure you don't disrupt other people's work. The machines don't |
| 76 |
need to be centrally administered, and you don't need root to |
| 77 |
install the daemon. |
| 78 |
<p> |
| 79 |
Depending on your project and infrastructure, compilation time could |
| 80 |
easily be more than halved. |
| 81 |
<p> |
| 82 |
Faster compilations give you the advantage of being able to do <tt>make |
| 83 |
clean; make all</tt> more frequently, which can catch bugs that |
| 84 |
might be hidden by incorrect Makefile dependencies. It allows test |
| 85 |
engineers to get builds to test faster. It makes nightly (or |
| 86 |
hourly? or continuous?) check builds more feasible, so bugs that are |
| 87 |
checked in can be caught and fixed with less disruption. |
| 88 |
<p> |
| 89 |
In a variation on this, you also have one big machine. Perhaps it |
| 90 |
primarily acts as a server or master build machine, but you can also |
| 91 |
use it to accelerate compilation on your workstation or laptop. |
| 92 |
|
| 93 |
|
| 94 |
<h2>sofa computing</h2> |
| 95 |
<p> |
| 96 |
At home, you like to use your laptop and wireless to program on the |
| 97 |
sofa or in the garden. It's convenient to keep all your working |
| 98 |
directories on the laptop so that you can take it with you wherever |
| 99 |
you go. |
| 100 |
<p> |
| 101 |
However, it's slow and gets hot when you build a large project. |
| 102 |
Fortunately, you also have a faster machine in your home office. |
| 103 |
<p> |
| 104 |
Using distcc, you can push most of the work of compilation onto the |
| 105 |
faster machine. You have the advantage of keeping all your source |
| 106 |
in one place, but compilation runs at the speed of your fast |
| 107 |
machine. |
| 108 |
|
| 109 |
|
| 110 |
<h2>working on embedded or small computers</h2> |
| 111 |
<p> |
| 112 |
You're developing on a small Linux machine, such as the |
| 113 |
<a href="http://rikkus.info/zaurus.html#distcc">Zaurus</a> or an embedded |
| 114 |
PC. It's large enough that you can run editors and work directly on |
| 115 |
it, but small enough that compilation is painfully slow. On the |
| 116 |
other hand, developing anywhere else is indirect, and necessitates |
| 117 |
continually copying files to and fro. |
| 118 |
<p> |
| 119 |
By running the distcc client on the small machine, you can shift |
| 120 |
most of the work onto a cross-compiler installed on a faster |
| 121 |
machine, but otherwise work directly on the box. |
| 122 |
</tr></table> |
| 123 |
<div class="thanks">Copyright © 2002–2004, 2006 Martin Pool. |
| 124 |
<p>Send comments to <tt>distcc(at)lists.samba.org</tt> |
| 125 |
</html> |