Comments on: How 37 Signals Deploys Their Software http://www.buzzwordcompliant.net/2008/10/22/how-37-signals-deploys-their-software/ Sun, 15 May 2011 19:07:41 +0000 hourly 1 http://wordpress.org/?v=3.0 By: Michael Buckbee http://www.buzzwordcompliant.net/2008/10/22/how-37-signals-deploys-their-software/comment-page-1/#comment-10398 Michael Buckbee Thu, 23 Oct 2008 13:52:02 +0000 http://www.buzzwordcompliant.net/2008/10/22/how-37-signals-deploys-their-software/#comment-10398 Thanks John, I fixed it. I should have caught it myself, it's not as if Amazon's some entity that's just giving away S3 and EC2 time. - Mike Thanks John, I fixed it. I should have caught it myself, it’s not as if Amazon’s some entity that’s just giving away S3 and EC2 time.

- Mike

]]> By: John Meredith http://www.buzzwordcompliant.net/2008/10/22/how-37-signals-deploys-their-software/comment-page-1/#comment-10397 John Meredith Thu, 23 Oct 2008 09:50:17 +0000 http://www.buzzwordcompliant.net/2008/10/22/how-37-signals-deploys-their-software/#comment-10397 The "Amazon Web Services" link should be .com instead of .org The “Amazon Web Services” link should be .com instead of .org

]]> By: Mark Imbriaco http://www.buzzwordcompliant.net/2008/10/22/how-37-signals-deploys-their-software/comment-page-1/#comment-10395 Mark Imbriaco Wed, 22 Oct 2008 19:48:15 +0000 http://www.buzzwordcompliant.net/2008/10/22/how-37-signals-deploys-their-software/#comment-10395 For the record, I said a couple of things that I realized after the fact were incorrect: 1. InnoDB hot backup doesn't block writes to the database while it's running, but it is very I/O intensive so your slave can definitely backlog while it runs. I've seen better performance with LVM snapshots using mylvmbackup. 2. We don't run the Phusion patched Ruby, at least not completely. We use their backport of the security patches and some GC patches from another source (http://railsbench.rubyforge.org/svn/trunk/railsbench/ruby186gc.patch), but we don't use their copy-on-write friendly garbage collector. For the record, I said a couple of things that I realized after the fact were incorrect:

1. InnoDB hot backup doesn’t block writes to the database while it’s running, but it is very I/O intensive so your slave can definitely backlog while it runs. I’ve seen better performance with LVM snapshots using mylvmbackup.

2. We don’t run the Phusion patched Ruby, at least not completely. We use their backport of the security patches and some GC patches from another source (http://railsbench.rubyforge.org/svn/trunk/railsbench/ruby186gc.patch), but we don’t use their copy-on-write friendly garbage collector.

]]>