[erlang-questions] Some notes on making a random erlang program (egitd) faster
Sat Feb 26 14:47:33 CET 2011
egitd was created by Tom Preston-Werner (@mojombo) for GitHub. Andrew used
it as a project example for performance tuning.
Design considerations aside from performance weren't part of the primary
goal of Andrew's experiment.
You should fork Andrew's egitd and experiment with best practices
refactoring and write a blog article ;)
On Sat, Feb 26, 2011 at 2:17 AM, Jay True <> wrote:
> Hello Andrew,
> I'm trying your egitd and found that there are two calling of conf
> module's function which should be egitd_conf instead.
> On Sat, Feb 12, 2011 at 11:21 AM, Andrew Thompson <>
> > 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:
> > http://andrew.hijacked.us/by_keyword/328/egit
> > Hopefully someone will find this useful and/or won't blame the failure
> > of egitd on erlang.
> > Andrew
> > ________________________________________________________________
> > erlang-questions (at) erlang.org mailing list.
> > See http://www.erlang.org/faq.html
> > To unsubscribe; mailto:
> erlang-questions (at) erlang.org mailing list.
> See http://www.erlang.org/faq.html
> To unsubscribe; mailto:
More information about the erlang-questions