[spohlenz]

I don't mean to dwell on the technical issues, but I'd be very curious to hear more about the performance issues you encountered that the Rails Core members couldn't resolve. Was there ever any resolution apart from downgrading to 2.x, and are there certain things that should be avoided in Rails 3.x?

[ahoyhere]

Whatever it was, it is gone now. This was Rails 3 early days… very early days. The problem was in the development environment only. It was a crazy memory leak — 50MB every page load or so. As you can imagine it because so unbearably slow we couldn't develop in it. Bizarrely it didn't manifest in production (even if we just flipped the bit to run mongrel — or was it nginx at the time ? — in production on the same dev computer/user/PATH, etc). You'd think that would make it easier to track down, but weirdly, it didn't.

I don't mind at all answering technical questions, ask away. What I object to is people who spot a jargon term or two they understand and fail to read all the surrounding paragraphs, and then lambast me for something they know nothing about. Which you clearly didn't do :)