We run a large rails app with over 500 instances spread out over 100 servers, and we use New Relic RPM to monitor the app's health.
Versions: Rails 2.3.2, Haml 3.0.25 Without loading the haml gem, we have a baseline average response rate of ~2.27 seconds. Then we add the following line to environment.rb: config.gem 'haml', :version => '3.0.25' After deploying the change, our response rate instantly jumps to ~4.11 seconds, and does not go down, even after an hour or so. We have no .haml templates or any other code changes besides the one line above. We would really love to start using haml, but with those numbers there is no way that we can make the jump. I browsed the source a bit and noticed that haml wraps a lot of actionview's helper methods (we use these extensively). Can this add up to a lot of overhead when you have requests coming in at the rate we do? Also has anything changed in the rails framework in more recent versions that allow haml to hook in more cleanly vs overriding all those methods? It is hard to believe haml is approaching version 3.1 with this big of a performance issue, so hopefully I missing something here. Please help shed some light! -- You received this message because you are subscribed to the Google Groups "Haml" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/haml?hl=en.
