[erlang-questions] Some notes on making a random erlang program (egitd) faster
Sat Feb 12 14:45:42 CET 2011
On 2011-02-11, at 23:51, Andrew Thompson <andrew@REDACTED> wrote:
> Just for something to do this week, I decided to pick a random erlang
> project that was a failure due to its speed and see if I could make it
> fast enough to compete. I picked egitd (the erlang git daemon that
> github wrote) because it was a fairly public failure. It took me ~4
> hours from first grabbing the code to get its performance very close to
> git-daemon. I also removed ~1500 LOC along the way.
> Here's the in-depth notes on what I did, as a series of blog articles:
> Hopefully someone will find this useful and/or won't blame the failure
> of egitd on erlang.
That was awesome Andrew! The fixes you found and the rate at which yoy verified them is prodigal.
I highly recommend that everyone on this list read Andrew's Optimizing egitd blog post series starting with http://andrew.hijacked.us/article/324/optimizing-egitd-introduction
Optimizing egitd is a clearly written dissection of a performance problem and a beautifully documented path to its resolution.
Congratulations Andrew and thank you for sharing your experience :)
More information about the erlang-questions