5 ms·

does this fix the abominably slow development with the asset pipeline (without the gems needed to hack it and speed it up)? Basically, can someone give me a wa

does this fix the abominably slow development with the asset pipeline (without the gems needed to hack it and speed it up)? Basically, can someone give me a way back into pre-3.1 asset pipeline slowdown ?

tmeasday 15y ago
Can you be more specific? Are you talking about rails startup time or SASS compilation? Or something else?
- sandGorgon 15y ago
  in dev mode, the asset pipeline induces extremely slow page loads in development (2-4 seconds per page locally) This has been the single biggest complaint against Rails 3.1 if you google for it. For e.g. take a look at http://stackoverflow.com/questions/8084006/serve-assets-directly-no-asset-pipeline-in-development http://stackoverflow.com/questions/8084006/serve-assets-dire... Similar questions have been addressed by either installing rails-dev-tweaks or by pre-compiling assets - which is then a problem if you're actually working on the UI/JS - which is where half the dev time is usually spent.
  - Corrado 15y ago
    Ah, I was wondering how come my development environment had slowed down so much in the past couple of releases. Had I known enough to check for it I probably would have found out about that rails-dev-tweaks Gem sooner. Anyway, yes I think that this release fixes those issues. However, there appears to be a problem with the SASS @import command and partials[1] so I haven't been able to fully test my system yet with all it's assets working properly. [1] https://github.com/rails/rails/issues/4041 https://github.com/rails/rails/issues/4041
  - ruckusing 15y ago
    I've noticed that using Passenger Standalone is faster than webrick / mongrel in dev mode using Asset Pipeline. Give it a shot.
    - jaylevitt 15y ago
      I just switched to pow to avoid the annoying content-length warnings in 1.9.3 webrick, and it's pretty darn zippy, debug-mode asset pipeline and all: curl get.pow.cx | VERSION=0.4.0-pre sh
  - tmeasday 15y ago
    Sure; no, I've seen the same kinds of problems. If you are interested, I posted in the comments to this gist (https://gist.github.com/1184843#gistcomment-65875 https://gist.github.com/1184843#gistcomment-65875) some changes that we made to our SASS files to markedly increase the compile time. For us it went from (depending on the machine) something like 40s down to a <5 seconds which was a massive improvement (CSS development was almost impossible for a while there).
- Stratego 15y ago
  There have been several issues with Sass (sass-rails) and the Asset Pipeline. Some of them involving Compass (https://github.com/chriseppstein/compass/issues/516#issuecomment-3212367 https://github.com/chriseppstein/compass/issues/516#issuecom...), some of them due to Sprockets (https://github.com/sstephenson/sprockets/pull/268#issuecomment-3212022 https://github.com/sstephenson/sprockets/pull/268#issuecomme...). They have indeed been crippling for front-end development, and majorly under-reported since this summer. So if you're facing any of these issues, please participate in the GitHub Issues threads I linked above and help the relevant teams diagnose/improve the problems.
aubergene 15y ago
I found it was really slow when assets were in debug. I generated a new rails app and copied the config from there and then merged in the settings from the old project I needed and it was super fast.

tmeasday 15y ago

Can you be more specific? Are you talking about rails startup time or SASS compilation? Or something else?

sandGorgon 15y ago
in dev mode, the asset pipeline induces extremely slow page loads in development (2-4 seconds per page locally) This has been the single biggest complaint against Rails 3.1 if you google for it. For e.g. take a look at http://stackoverflow.com/questions/8084006/serve-assets-directly-no-asset-pipeline-in-development http://stackoverflow.com/questions/8084006/serve-assets-dire... Similar questions have been addressed by either installing rails-dev-tweaks or by pre-compiling assets - which is then a problem if you're actually working on the UI/JS - which is where half the dev time is usually spent.
- Corrado 15y ago
  Ah, I was wondering how come my development environment had slowed down so much in the past couple of releases. Had I known enough to check for it I probably would have found out about that rails-dev-tweaks Gem sooner. Anyway, yes I think that this release fixes those issues. However, there appears to be a problem with the SASS @import command and partials[1] so I haven't been able to fully test my system yet with all it's assets working properly. [1] https://github.com/rails/rails/issues/4041 https://github.com/rails/rails/issues/4041
- ruckusing 15y ago
  I've noticed that using Passenger Standalone is faster than webrick / mongrel in dev mode using Asset Pipeline. Give it a shot.
  - jaylevitt 15y ago
    I just switched to pow to avoid the annoying content-length warnings in 1.9.3 webrick, and it's pretty darn zippy, debug-mode asset pipeline and all: curl get.pow.cx | VERSION=0.4.0-pre sh
- tmeasday 15y ago
  Sure; no, I've seen the same kinds of problems. If you are interested, I posted in the comments to this gist (https://gist.github.com/1184843#gistcomment-65875 https://gist.github.com/1184843#gistcomment-65875) some changes that we made to our SASS files to markedly increase the compile time. For us it went from (depending on the machine) something like 40s down to a <5 seconds which was a massive improvement (CSS development was almost impossible for a while there).
Stratego 15y ago
There have been several issues with Sass (sass-rails) and the Asset Pipeline. Some of them involving Compass (https://github.com/chriseppstein/compass/issues/516#issuecomment-3212367 https://github.com/chriseppstein/compass/issues/516#issuecom...), some of them due to Sprockets (https://github.com/sstephenson/sprockets/pull/268#issuecomment-3212022 https://github.com/sstephenson/sprockets/pull/268#issuecomme...). They have indeed been crippling for front-end development, and majorly under-reported since this summer. So if you're facing any of these issues, please participate in the GitHub Issues threads I linked above and help the relevant teams diagnose/improve the problems.

aubergene 15y ago

I found it was really slow when assets were in debug. I generated a new rails app and copied the config from there and then merged in the settings from the old project I needed and it was super fast.