News for hackers. Stuff that matters.
Re:Github and Engineyard part ways by jcapote on Friday September 11, 2009 @03:21PM (#817938)
That assumes that Github is slow because of their hosting (Engineyard) and not because of how it's written.

I dunno, it could go either way for me: "Engineyard drops Github for being too costly" vs "Github needs better hosting, so we're dropping Engineyard"

Re:Github and Engineyard part ways by jhancock on Friday September 11, 2009 @03:30PM (#817953)
Its probably more about costs for both sides. I doubt that EY is _slow_ without regard to cost. Just that instead of rewritting GitHub's web app to deal with inherent performance issues, it makes more sense to throw more hardware at the problem. There does come a point where owning more of your server stack makes more financial sense.
Re:Github and Engineyard part ways by fnid on Friday September 11, 2009 @04:00PM (#818009)
It is going to be interesting to see how the performance of Github and their freemium offering changes when they start paying for infrastructure somewhere else. Unless they can smooth talk another host into giving them free infrastructure.
Re:Github and Engineyard part ways by jhancock on Friday September 11, 2009 @04:03PM (#818013)
Based on replies from my support queries about performance, they are aware that paying customers expect better/more-consistent performance than what we've had of late.
Re:Github and Engineyard part ways by fnid on Friday September 11, 2009 @04:15PM (#818034)
I see, so even if they did pay, it still wouldn't be fast enough. So free even has its costs, in terms of dissatisfied customers.