News for hackers. Stuff that matters.

A comment on Rails 3.2.13 - Performance regressions and major bugs. Parent comment

Re:Rails 3.2.13 - Performance regressions and major bugs by josephlord on Wednesday March 20, 2013 @06:28PM (#5410906)
To be honest I don't know and I wouldn't have negatively responded to a comment indicating that or questioning it. However reading the article it sounds like it is an issue resolving asset paths so may affect you even when assets are precompiled.

Performance Regressions

There are performance regressions in 3.2.13 for both view loading and asset loading. Rails 3.2.13 changed the way assets paths are resolved, handing that task to Sprockets instead of resolving internally, which seems to be the cause of the performance issues.

[ Parent | on HN ]
Re:Rails 3.2.13 - Performance regressions and major bugs by fredwu on Wednesday March 20, 2013 @07:15PM (#5411298)
Actually, the performance degradation to the precompiled assets is minimal - for a typical production environment it only effects your asset compiling time as the assets are served statically from your public directory.
[ Parent | on HN ]