assets:precompile takes a long time

Question

assets:precompile takes a long time

sandergarretsen opened this issue 11 years ago · 9 comments

"Since version 4.1.3, non-digested assets of ckeditor-rails will simply be copied after digested assets were compiled."

I read the closed issues about the asset-pipeline in rails4 and Eric's solution.
Is this the reason why the task takes about 5 minutes during every deploy?

Answer 1 · 2014-01-30T02:00:16.000Z

I don't think so since the task of ckeditor-rails will check if the old one exists or expires.
https://github.com/tsechingho/ckeditor-rails/blob/master/lib/ckeditor-rails/tasks.rake#L9
And the copy process is very fast action.

It might be some other compile processes taking your time on each deploy.

Answer 2 · 2014-02-05T18:47:43.000Z

I'm having a similar issue -- asset precompilation is taking a very long time, and the hangs are clearly on pieces of the ckeditor code. One thing that might help would be the ability to limit what is included in the ckeditor install so that we're not having to precompile too much if we don't need to?

Answer 3 · 2014-02-05T21:39:52.000Z

I'm also pretty sure that this gem is causing my problems. When I add this gem, assets:precompile takes about 12 minutes. When I remove it, it's just a couple of seconds.

I'm not experienced enough to say if this is normal behavior or not. But it seems long to me...

Probably it's not really the gem causing it, but just the consequence of adding this many files to the asset pipeline?

Answer 4 · 2014-02-11T06:07:53.000Z

I'm having the same issue right now and I'm pretty sure this gem is what made the precompilation very slow. It has almost been 30 minutes since I deployed to Heroku and it still hasn't finished yet. I'll try to use an older version and let you know what I find.

Answer 5 · 2014-02-11T17:13:37.000Z

Same here, it's taking a long time compiling all files under ckeditor/lang (and I don't need to support all those languages). Any way to avoid this?

Answer 6 · 2014-02-12T03:45:22.000Z

This is my today's deploy log of capistrano 3. It's not fresh deployment. it's deployed to my own machine, not heroku, not virtual machine in laptop.

https://gist.github.com/tsechingho/8949668

I can't repeat your situation.

Answer 7 · 2014-02-12T08:36:52.000Z

Maybe it's a problem with Heroku? I'll try to use turbosprockets.

Answer 8 · 2014-02-12T08:44:01.000Z

Probably not, I have the same problem on my ubuntu-vps.

One thing I found out is that if I run the "rake assets:precompile" task manually, its very fast...
Looks like I only have this problem when deploying with capistrano

Answer 9 · 2014-02-12T13:05:54.000Z

Ok, I finaly found a solution for my problem. It had nothing to do with this gem but with my capistrano-rails configuration.

These posts helped me:
capistrano/rails#47
ndbroadbent/turbo-sprockets-rails3#61

I did not symlink the tmp/cache directory in my deploy.rb. This configuration solved my problem:

set :linked_dirs, %w{bin log tmp/pids tmp/cache tmp/sockets vendor/bundle public/uploads public/assets}