Closed dangerbell closed 13 years ago
We're using Rails 2.3.11, and aren't experiencing slow load times at all. I doubt Jammit is your problem. But of course, the scientific method is always best: why not try disabling and re-enabling Jammit, and comparing the load times before and after?
If you want to get to the root of the problem, you can wrap your Rails boot script in a ruby-prof profile, and get detailed information about what's slow:
Looks like my slow down is caused by a particularly problematic gem called Desert. Using Jammit is gonna have to wait until I can finally remove it.
By slow I mean in the 5 minute range. I had about a 30 second start up time before. Then I installed Jammit to test it out and started getting ridiculously long load times. Has anyone else seen this?
I'm running a Rails 2.3.2 project is there an incompatibility with this version?
I can't tell if Jammit is causing it. Is there a way to get log output from Jammit?