I had it coming…

Just to recap – various stuff that runs Ravelry and my opinion on each:

  • Ruby on Rails 2: Love it. Moving to 2.1 for the named scopes (and because I’m on Edge somewhere between 2 and 2.1)
  • Thin : stable. A little nicer than Mongrel.
  • nginx : rocks. (ie. fast, stable, does what I want, trouble-free)
  • haproxy: rocks (ditto).
  • Sphinx : rocks (ditto).
  • backgroundrb : the new and different version ain’t bad. Give it a try.
  • Ferret / acts_as_ferret : phased out. Kind of a pain, slow to reindex. The DRb business made things shaky at times (ie. ferret server goes down, badness ensues).
  • MySQL 5.1.24 (rc2) and the innodb plugin: argh. Had deadlocked for no apparent reason, killing processes doesn’t help, MySQL hangs, must kill MySQL :( This has happened 3 times in the same number of weeks. MySQL 5.0.something worked great for a year but I’m a hopeless magpie sometimes. On the plus side, MySQL 5.1 seems to recover faster and slaves don’t lose their minds during the kill/restart. heh. I’m blaming MySQL and not the plugin (just a hunch, I have no evidence). In any case, wait for the next release.

    Next time I’ll have to grab processlist and innodb status output so I can actually try to find/report the bug. Doh. I started up Maatkit’s mk-deadlock-logger, so hopefully that will catch it…

Comments (6)

  1. You can use has_finder to get the benefit of named_scopes in rails 2.0. I used to “ride edge” before rails 2.0 came out, but stopped when it was released.

    Glad I didn’t upgrade MySQL when you first talked about it :)

    Monday, May 12, 2008 at 6:35 pm #
  2. Was MySQL crapping out what caused us all to see Bob earlier today?

    Monday, May 12, 2008 at 7:41 pm #
  3. Tom H wrote:

    Well, there’s always PostgreSQL, which is working rockingly for us in a Rails 2 environment. Now that MySQL is owned by the evil Oracle, maybe it’s time to switch ;-) In any case, I feel your pain. May the force be with you.

    Tuesday, May 13, 2008 at 5:03 pm #
  4. Lara wrote:

    hey :) I wanna teach myself Ruby. Any suggestions on a good place to start? Sites? Books? Hook a girl up! :)

    Monday, May 19, 2008 at 10:31 am #
  5. John Dalton wrote:

    Wow, scary news about the MySQL crashes. I’ve been seriously considering testing it on one of our slaves, as I think the compression options in the new inno_db plugin could potentially help us a lot with disk IO. But I’d really rather not have to deal with a crashing database server ;)

    Thursday, May 29, 2008 at 1:11 am #
  6. gleek wrote:

    thanks for this. i’ve always wondered what was behind all of ravelry. i’m a PHP and perl girl myself. i wish i had jumped on the ruby wagon a couple of years ago!

    Sunday, June 29, 2008 at 6:12 pm #

Trackbacks/Pingbacks (2)

  1. Quick update: Ravelry runs on…. < Code Monkey Island on Tuesday, March 10, 2009 at 11:30 pm

    […] March, I wrote a tiny post that listed a few of the pieces that run Ravelry along with my opinion of each. Here is a update to […]

  2. Ravelry Runs On - 2010 -- Code Monkey Island on Wednesday, March 24, 2010 at 9:34 am

    […] that it’s time for the 3rd annual “Ravelry Runs On” roundup. The last two were in March 2008 and March […]