Re: Preparing the m68k port for the future.
On Fri, Jan 13, 2006 at 02:38:02PM +0100, Ingo Juergensmann wrote:
> On Fri, Jan 13, 2006 at 02:09:19PM +0100, Wouter Verhelst wrote:
> > Additionally, Ingo told me when the mail about that meeting had come out
> > that he'd already tried such a setup in the past (I didn't know that
> > when we were in Helsinki, but it was before that), and that his setup,
> > IIRC, was in fact slower than a native build because of the overhead of
> > the network call to start the compiler--At least that's how I recall his
> > explanation. I don't remember the details; if you have any questions,
> > please ask him.
>
> Uhm, well, yes, I tried a distcc setup on m68k. Actually it's the opposite:
> Of course there's a overhead via network (I was using two m68ks with 450 km
> and 2 DSL dialups inbetween), but the test (kernel compile) showed approx. a
> total of 40-50% gain in build time.
[...]
Ah. Hmm. Well, then I must have misremembered somehow. Sorry about that.
That would indeed change a few things, of course. But, still, I do think
that the ability to start using hardware that is 4-8 times the speed of
what we currently have is a better way to improve the average speed of
our build daemons than to start using complex setups such as distcc. If
that turns out to not be enough, we can still try distcc then.
--
.../ -/ ---/ .--./ / .--/ .-/ .../ -/ ../ -./ --./ / -.--/ ---/ ..-/ .-./ / -/
../ --/ ./ / .--/ ../ -/ ..../ / -../ ./ -.-./ ---/ -../ ../ -./ --./ / --/
-.--/ / .../ ../ --./ -./ .-/ -/ ..-/ .-./ ./ .-.-.-/ / --/ ---/ .-./ .../ ./ /
../ .../ / ---/ ..-/ -/ -../ .-/ -/ ./ -../ / -/ ./ -.-./ ..../ -./ ---/ .-../
---/ --./ -.--/ / .-/ -./ -.--/ .--/ .-/ -.--/ .-.-.-/ / ...-.-/
Reply to: