Walter Bright wrote:
Andreas Ericsson wrote:
Walter Bright wrote:
1) You wind up having to implement the complex, dirty details of
things yourself. The consequences of this are:
a) you pick a simpler algorithm (which is likely less efficient -
I run across bubble sorts all the time in code)
b) once you implement, tune, and squeeze all the bugs out of those
complex, dirty details, you're reluctant to change it. You're
reluctant to try a different algorithm to see if it's faster. I've
seen this effect a lot in my own code. (I translated a large body of
my own C++ code that I'd spent months tuning to D, and quickly
managed to get significantly more speed out of it, because it was
much simpler to try out different algorithms/data structures.)
I haven't seen this in the development of git, although to be fair, you
didn't mention the number of developers that were simultaneously working
on your project.
On my project, one. But I've seen this problem repeatedly in other
projects that had multiple developers. For example, I used to use
version 1 of an assembler. It was itself written entirely in assembler.
It ran *incredibly* slowly on large asm files. But it was written in
assembler, which is very fast, so how could that be?
Turns out, the symbol table used internally was a linear one. A linear
symbol table is easy to implement, but doesn't scale well at all. A
linear symbol table was implemented because it was just harder to do
more advanced symbol table algorithms in assembler. In this case, a
higher level language re-implementation made the assembler much faster,
even though that implementation was SLOWER in every detail. It was
faster overall, because it was easier to develop faster algorithms.
Well, when the ease-of-coding vs the exec-speed of D vs C is that of
C vs asm, C will be dead fairly soon. However, since C is so ingrained
in every language designer's head, I find that unlikely to happen any
time soon.
Opensource projects with many contributors (git, linux) work differently,
since one or a few among the plethora of authors will almost always be
a true expert at the problem being solved.
That is a nice advantage. I don't think many projects can rely on having
the best in the business working on them, though <g>.
True that. I know a fair few projects that could have done with borrowing
one or two proper gurus, but even opensource programmers are selfish in
that we usually only work for something that benefits ourselves.
The point is that, given enough developers, *someone* is bound to
find an algorithm that works so well that it's no longer worth
investing time to even discuss if anything else would work better,
either because it moves the performance bottleneck to somewhere else
(where further speedups would no longer produce humanly measurable
improvements), or because the action seems instantanous to the user
(further improvements simply aren't worth it, because no valuable
resource will be saved from it).
Sure, but I suggest that few projects reach this maxima.
True again, but given what I said above holds, it would be madness to
move from the lingua franca of oss hacking to a less common one, as it
would mean fewer eyes on the code.
Case in point:
ld, the gnu linker. It's terribly slow. To see how slow it is, compare
it to optlink (the 15 years old one that comes with D for Windows). So I
don't believe there is anything inherent about linking that should make
ld so slow. There's some huge leverage possible in speeding up ld
(spreading out that saved time among all the gnu developers).
So while git may have reached a maxima in performance, I don't think
this principle is applicable in general, even for very widely used open
source projects that would profit greatly from improved performance.
Interesting. I recently did a spot of work comparing various string-hashing
algorithms. Perhaps I should head over to the ld camp and see if I can help.
--
Andreas Ericsson andreas.ericsson@xxxxxx
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
