Debian Codegraph @

doc/web/results.html

raw
1 <html>
2 <head><title>distcc testimonials</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">scenarios</a></li>
24 <li><a href="results.html"><b>testimonials</b></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">distcc testimonials</h1>
55
56 <p align=right>
57 <em>C lets you shoot yourself in the foot, and distcc gives
58 you a chaingun.</em>
59
60 <p>
61 For speeding up our builds we use and
62 recommend distcc to allow us to distribute compilation across
63 two or more machines (i.e. a laptop and a desktop). distcc can
64 be set up in no time and if like us you're continuously and
65 repeatedly building lots of code it'll save you hours if not
66 days of waiting around for compiles to finish. Also check out
67 <a href="https://ccache.dev/">ccache</a>.
68 &mdash; The
69 <a href=http://www.rosegardenmusic.com/resources/links/>Rosegarden</a>
70 music software developers.
71
72 <hr>
73
74 <p>
75 Paul Daniels:
76 <p>
77 I'd just like to extend my thanks to the creators (and maintainers ;-)
78 of distcc and associated projects. My projects here are getting
79 rather large in size (relative) such that I have to wait too long
80 between the process of tweak-build-test-*groan* (repeat). 5 mins of
81 distcc across a few unused boxes in this office and everything was
82 much better ... only trouble now is that I no longer have an excuse to
83 walk the hallways and make coffee *curse*.
84 <p>
85 Seriously though, great project, simple to use, generates real results
86 &mdash; hallmarks of a indispensable utility.
87
88 <hr>
89
90 <p>
91 Jens Mayer:
92 distcc rocks. Thank you very much for your excellent work!
93
94
95
96
97
98
99 <hr>
100 <p>
101 Alex Landa:
102 <p>
103
104 It's a scorcher!
105
106 <p>
107 I originally also had a rather low-memory (24MB) Pentium S-90 in the chain.
108 I removed this because it was swapping and its old hard drive was making
109 a total racket. I'm not sure if it slowed the whole cluster, but it seemed
110 to. Learning which order to put the machines in was something that I got
111 the hang of rather quickly. The Xbox did most of the hard work.
112
113
114 <hr>
115
116
117 <p>
118 Richard Bown:
119
120 <p>
121 Previously building on desktop or laptop - times around 25-30mins for
122 complete build. Really getting me down, decided I needed to upgrade my
123 hardware. Then after consideration thought why should I be spending
124 more money on hardware when I've already got so much lying around?
125 Quick search failed to find distcc but instead found old (defunct)
126 project called "doozer" - tried, talked to the author, he recommended
127 distcc. Downloaded yesterday, up and running in no time. First
128 attempts:
129
130 <p>
131 With main desktop and laptop: 15mins (make -j 4)
132 <br>With main desktop, laptop and desktop 2: 18mins (make -j 8)
133 <br>Jiggled build order and with main desktop,
134 laptop and desktop 2: 13mins (make -j 4)
135
136 <p>
137 Excellent results after some prodding about.
138
139 <p>
140 6. Any other observations:
141
142 <p>
143 Significant improvements with just the two machines (as noted in the
144 distcc web pages) and good enough to stop me from buying anything else
145 for a while. Will continue to play around with configuration settings.
146 Considering putting another (older) machine into the cluster but wonder
147 whether it'll make enough of a difference. Current hard limit to
148 improving times much further is the link stage which can take almost
149 two mins just by itself.
150
151 <p>
152 Great piece of software. Many thanks,
153 <br>Richard Bown
154 <br>--
155 <br>Rosegarden. Music Software For Linux
156
157 <hr>
158
159 <p>
160 Thank you very much for this great tool. Our only regret is not to have used it before.
161 &mdash;
162 Guillaume LAURENT,
163 <a href=http://www.telegraph-road.org/>telegraph-road.org</a>
164
165 <hr>
166
167 <p>
168 Stephane Eranian, hp (linux ia64 maintainer):
169
170 <p>
171 Yes, distcc is really nice. I have been using it for a month or so
172 for my kernel compiles using a cluster of Itanium 2 machines. What
173 I like is that it is really easy to setup. The danger with the
174 approach is that you can easily overload your local (master) host.
175 As for kernel compiles for 2.5, there are a lot of ld steps
176 which are still all done on the master node. Besides that you
177 can really feel the speed difference. I need to take a look at ccache
178 now that you mention it.
179
180 <hr>
181 <p>
182 Grant Grundler, hp:
183
184 <p>
185 (Endorsement): Stephane and I played around with just distcc for
186 2.4 ia64 kernels on a smaller cluster of rx2600 (dual CPU).
187 The "master" runs out of CPU around -j16 (8 hosts).
188 But that resulted in 66 second kernel builds.
189 And distcc really is trivial to setup.
190
191
192 <hr>
193
194
195 <p>
196 Hey Martin-
197
198 <p>
199 I've only been using distcc for a little while, on and off, and have
200 only been on this mailing list for a month or so... but I've gotta say,
201 you're doing one hell of a nice job. It seems extremeley rare to see
202 one-man projects with devs so open about what they're doing, why they're
203 doing it, and what potential problems might be these days...
204 <p>
205
206 You're doing a bang up job and distcc totally rocks. Keep up the good
207 work!
208
209 <p>
210 Rob
211
212
213
214 <hr>
215 <p>
216 distcc just rocks for doing regression tests!
217
218
219 <hr>
220
221 <p>
222 J.T. Conklin:
223
224 <p>
225 I'm in the midst of converting the build infrastructure at work from
226 using recursive gmake to Scons, and
227 thought it might be useful to share my experiences.
228
229 <p>
230 The gmake build scheme we have been using is much like many others I
231 have encountered over the years. A list of subdirectories are built
232 sequentially by iterating over the list and spawning a new make for
233 each. One problem with this approach is that the end of each module/
234 subdirectory becomes a synchronization point. For example, when there
235 are fewer files to compile (in a given module) than you have processes
236 in your pool, you're not taking full advantage of your build farm.
237
238 <p>
239 This deficiency can be addressed by rewriting your makefiles to avoid
240 recursion (Cf Peter Miller's paper
241 "<a
242 href="http://www.tip.net.au/~millerp/rmch/recu-make-cons-harm.html">Recursive
243 Make Considered Harmful</a>"
244 or by using another tool (like scons, jam, etc.) that constructs a full
245 dependency graph before building.
246
247 <p>
248 Here's a real-world example that demonstrates the advantages. Our
249 source code is about 600,000 lines of C++, with a small amount of C
250 and assembly thrown in. There are sixteen libraries, a dozen or so
251 executables (including four very large ones), etc.
252 <p>
253
254 On a AMD Athlon 2000+, using our old recursive gmake with -j4 (mainly
255 to hide i/o latency):
256 <br> real: 21m26.052s
257 <br> user: 19m44.063s
258 <br> sys: 1m28.127s
259
260 <p>
261 On a distcc build farm including the above AMD machine, plus 2 1.0GHz
262 PIII machines and 2 Dual 1.0GHz PIII machines with gmake -j20:
263 <br> real: 10m33.496s
264 <br> user: 5m34.436s
265 <br> sys: 1m0.731s
266
267 <p>
268 Our scons build on the single AMD machine with -j4:
269 <br> real: 13m52.052s
270 <br> user: 12m54.470s
271 <br> sys: 0m43.463s
272
273 <p>
274 And finally, scons -j20 on the distcc build farm:
275 <br> real: 3m47.938s
276 <br> user: 3m16.116s
277 <br> sys: 0m35.347s
278
279 <p>
280 While distcc alone more than doubled the performance, distcc plus a
281 build scheme that takes full advantage of build parallelism really
282 lets it shine by speeding up the build more than 5 times.
283
284 <hr>
285
286 <p>
287 distcc was too easy to setup. You should add some obscure dependency so
288 its a bit more difficult to get running. Nice job on a great util!!
289
290 <p>
291 Only downside is that I am tempted to buy more boxes now ;)
292 &mdash; Justin Kirby, openaether.org:
293
294
295 <hr>
296
297
298 <p>
299 distcc is awesome: easy install, no maintenance, works right. It's
300 saved us a lot of time, and the price sure beats that of Trolltech's
301 Teambuilder!
302
303 <hr>
304
305 <p>
306 I have a Sunblade 100 on my desktop and it
307 takes 4 minutes to compile one project of mine. Using 3 public Sunblade
308 1000's it now only takes 1 minute. Thank You, Thank You, Thank You.
309
310 <p>
311 -- Shane McDaniel, MIT
312 </tr></table>
313 <div class="thanks">Copyright &copy; 2002&ndash;2004, 2006 Martin Pool.
314 <p>Send comments to <tt>distcc(at)lists.samba.org</tt>
315 </html>