With the release of 3.1, it seems that things have drastically changed in the development workflow. With the asset pipeline enabled, and the likes of this in my layouts: = stylesheet_link_tag ''application'', :debug => Rails.env.development? = javascript_include_tag ''application'', :debug => Rails.env.development? ...every single css, js and image gets re-compiled on every single request. This takes forever. My dev log is mostly comprised of this: Started GET "/assets/jquery-ui-1.8.16.custom.css?body=1" for 127.0.0.1 at 2011-08-31 14:04:04 -0400 Served asset /jquery-ui-1.8.16.custom.css - 304 Not Modified (0ms) It seems to me that the dev rails server (both webrick, and passenger), is handling the request of every asset. It didn''t work this way in 3.0.x. While it clearly says 304 (0ms) I can attest that the overall time to process a page (and all its assets) is *significantly* longer. Here''s my application.rb and development.rb - they''re basically the 3.1 defaults. http://stackoverflow.com/questions/7248911/rails-3-1-force-development-assets-to-get-served-up-like-they-were-in-3-0-x So is there a solution here? Even if I didn''t have :debug => true in my javascript/stylesheet tag, the JS and CSS files would still have to be complied/generated as well as every image - which is still a significant regression. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
In development it recompiles with every reload. In production it only compiles when the files change and serves up the cached version otherwise. Dieter Lunn http://ubiety.ca On Wed, Aug 31, 2011 at 1:12 PM, Josh <josh.m.sharpe-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> With the release of 3.1, it seems that things have drastically changed > in the development workflow. > > With the asset pipeline enabled, and the likes of this in my layouts: > > = stylesheet_link_tag ''application'', :debug => Rails.env.development? > = javascript_include_tag ''application'', :debug => > Rails.env.development? > > ...every single css, js and image gets re-compiled on every single > request. This takes forever. > > My dev log is mostly comprised of this: > > Started GET "/assets/jquery-ui-1.8.16.custom.css?body=1" for 127.0.0.1 > at 2011-08-31 14:04:04 -0400 > Served asset /jquery-ui-1.8.16.custom.css - 304 Not Modified (0ms) > > It seems to me that the dev rails server (both webrick, and > passenger), is handling the request of every asset. It didn''t work > this way in 3.0.x. While it clearly says 304 (0ms) I can attest that > the overall time to process a page (and all its assets) is > *significantly* longer. > > Here''s my application.rb and development.rb - they''re basically the > 3.1 defaults. > > http://stackoverflow.com/questions/7248911/rails-3-1-force-development-assets-to-get-served-up-like-they-were-in-3-0-x > > So is there a solution here? Even if I didn''t have :debug => true in > my javascript/stylesheet tag, the JS and CSS files would still have to > be complied/generated as well as every image - which is still a > significant regression. > > -- > You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. > To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en. > >-- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
I understand the difference between dev and prod. The issue here is that in 3.0, a dev page load took half a second or less. It now takes upwards of 5 seconds. On Aug 31, 2:15 pm, Dieter Lunn <coder2...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> In development it recompiles with every reload. In production it only > compiles when the files change and serves up the cached version > otherwise. > > Dieter Lunnhttp://ubiety.ca > > > > > > > > On Wed, Aug 31, 2011 at 1:12 PM, Josh <josh.m.sha...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > With the release of 3.1, it seems that things have drastically changed > > in the development workflow. > > > With the asset pipeline enabled, and the likes of this in my layouts: > > > = stylesheet_link_tag ''application'', :debug => Rails.env.development? > > = javascript_include_tag ''application'', :debug => > > Rails.env.development? > > > ...every single css, js and image gets re-compiled on every single > > request. This takes forever. > > > My dev log is mostly comprised of this: > > > Started GET "/assets/jquery-ui-1.8.16.custom.css?body=1" for 127.0.0.1 > > at 2011-08-31 14:04:04 -0400 > > Served asset /jquery-ui-1.8.16.custom.css - 304 Not Modified (0ms) > > > It seems to me that the dev rails server (both webrick, and > > passenger), is handling the request of every asset. It didn''t work > > this way in 3.0.x. While it clearly says 304 (0ms) I can attest that > > the overall time to process a page (and all its assets) is > > *significantly* longer. > > > Here''s my application.rb and development.rb - they''re basically the > > 3.1 defaults. > > >http://stackoverflow.com/questions/7248911/rails-3-1-force-developmen... > > > So is there a solution here? Even if I didn''t have :debug => true in > > my javascript/stylesheet tag, the JS and CSS files would still have to > > be complied/generated as well as every image - which is still a > > significant regression. > > > -- > > You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. > > To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > For more options, visit this group athttp://groups.google.com/group/rubyonrails-talk?hl=en.-- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
Consider yourself lucky, I had to deal with 5 mins on first load recently. Take a look at the rails-dev-tweaks gem, it helps a lot. In addition to that make sure that you don''t autoload all the models if you use mongoid. On Wed, Aug 31, 2011 at 11:21 AM, Josh <josh.m.sharpe-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> I understand the difference between dev and prod. > > The issue here is that in 3.0, a dev page load took half a second or > less. It now takes upwards of 5 seconds. > > On Aug 31, 2:15 pm, Dieter Lunn <coder2...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > In development it recompiles with every reload. In production it only > > compiles when the files change and serves up the cached version > > otherwise. > > > > Dieter Lunnhttp://ubiety.ca > > > > > > > > > > > > > > > > On Wed, Aug 31, 2011 at 1:12 PM, Josh <josh.m.sha...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > > With the release of 3.1, it seems that things have drastically changed > > > in the development workflow. > > > > > With the asset pipeline enabled, and the likes of this in my layouts: > > > > > = stylesheet_link_tag ''application'', :debug => Rails.env.development? > > > = javascript_include_tag ''application'', :debug => > > > Rails.env.development? > > > > > ...every single css, js and image gets re-compiled on every single > > > request. This takes forever. > > > > > My dev log is mostly comprised of this: > > > > > Started GET "/assets/jquery-ui-1.8.16.custom.css?body=1" for 127.0.0.1 > > > at 2011-08-31 14:04:04 -0400 > > > Served asset /jquery-ui-1.8.16.custom.css - 304 Not Modified (0ms) > > > > > It seems to me that the dev rails server (both webrick, and > > > passenger), is handling the request of every asset. It didn''t work > > > this way in 3.0.x. While it clearly says 304 (0ms) I can attest that > > > the overall time to process a page (and all its assets) is > > > *significantly* longer. > > > > > Here''s my application.rb and development.rb - they''re basically the > > > 3.1 defaults. > > > > >http://stackoverflow.com/questions/7248911/rails-3-1-force-developmen. > .. > > > > > So is there a solution here? Even if I didn''t have :debug => true in > > > my javascript/stylesheet tag, the JS and CSS files would still have to > > > be complied/generated as well as every image - which is still a > > > significant regression. > > > > > -- > > > You received this message because you are subscribed to the Google > Groups "Ruby on Rails: Talk" group. > > > To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org > . > > > To unsubscribe from this group, send email to > rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > > For more options, visit this group athttp:// > groups.google.com/group/rubyonrails-talk?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Talk" group. > To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > To unsubscribe from this group, send email to > rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > For more options, visit this group at > http://groups.google.com/group/rubyonrails-talk?hl=en. > >-- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
That sounds horrible. I''m seeing this occur on every page load, not just the first one. On Aug 31, 2:26 pm, Martin Wawrusch <mar...-qs6+VQBngv1Wk0Htik3J/w@public.gmane.org> wrote:> Consider yourself lucky, I had to deal with 5 mins on first load recently. > Take a look at the rails-dev-tweaks gem, it helps a lot. In addition to > that make sure that you don''t autoload all the models if you use mongoid. > > > > > > > > On Wed, Aug 31, 2011 at 11:21 AM, Josh <josh.m.sha...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > I understand the difference between dev and prod. > > > The issue here is that in 3.0, a dev page load took half a second or > > less. It now takes upwards of 5 seconds. > > > On Aug 31, 2:15 pm, Dieter Lunn <coder2...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > > In development it recompiles with every reload. In production it only > > > compiles when the files change and serves up the cached version > > > otherwise. > > > > Dieter Lunnhttp://ubiety.ca > > > > On Wed, Aug 31, 2011 at 1:12 PM, Josh <josh.m.sha...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > > > With the release of 3.1, it seems that things have drastically changed > > > > in the development workflow. > > > > > With the asset pipeline enabled, and the likes of this in my layouts: > > > > > = stylesheet_link_tag ''application'', :debug => Rails.env.development? > > > > = javascript_include_tag ''application'', :debug => > > > > Rails.env.development? > > > > > ...every single css, js and image gets re-compiled on every single > > > > request. This takes forever. > > > > > My dev log is mostly comprised of this: > > > > > Started GET "/assets/jquery-ui-1.8.16.custom.css?body=1" for 127.0.0.1 > > > > at 2011-08-31 14:04:04 -0400 > > > > Served asset /jquery-ui-1.8.16.custom.css - 304 Not Modified (0ms) > > > > > It seems to me that the dev rails server (both webrick, and > > > > passenger), is handling the request of every asset. It didn''t work > > > > this way in 3.0.x. While it clearly says 304 (0ms) I can attest that > > > > the overall time to process a page (and all its assets) is > > > > *significantly* longer. > > > > > Here''s my application.rb and development.rb - they''re basically the > > > > 3.1 defaults. > > > > >http://stackoverflow.com/questions/7248911/rails-3-1-force-developmen. > > .. > > > > > So is there a solution here? Even if I didn''t have :debug => true in > > > > my javascript/stylesheet tag, the JS and CSS files would still have to > > > > be complied/generated as well as every image - which is still a > > > > significant regression. > > > > > -- > > > > You received this message because you are subscribed to the Google > > Groups "Ruby on Rails: Talk" group. > > > > To post to this group, send email to rubyonrails-talk@googlegroups.com > > . > > > > To unsubscribe from this group, send email to > > rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > > > For more options, visit this group athttp:// > > groups.google.com/group/rubyonrails-talk?hl=en. > > > -- > > You received this message because you are subscribed to the Google Groups > > "Ruby on Rails: Talk" group. > > To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > To unsubscribe from this group, send email to > > rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > For more options, visit this group at > >http://groups.google.com/group/rubyonrails-talk?hl=en.-- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
You may just move all static assets to public folder. That would get them loaded without involving asset pipeline. Correct me, if I''m wrong. On Aug 31, 10:30 pm, Josh <josh.m.sha...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> That sounds horrible. I''m seeing this occur on every page load, not > just the first one. > > On Aug 31, 2:26 pm, Martin Wawrusch <mar...-qs6+VQBngv1Wk0Htik3J/w@public.gmane.org> wrote: > > > > > > > > > Consider yourself lucky, I had to deal with 5 mins on first load recently. > > Take a look at the rails-dev-tweaks gem, it helps a lot. In addition to > > that make sure that you don''t autoload all the models if you use mongoid. > > > On Wed, Aug 31, 2011 at 11:21 AM, Josh <josh.m.sha...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > > I understand the difference between dev and prod. > > > > The issue here is that in 3.0, a dev page load took half a second or > > > less. It now takes upwards of 5 seconds. > > > > On Aug 31, 2:15 pm, Dieter Lunn <coder2...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > > > In development it recompiles with every reload. In production it only > > > > compiles when the files change and serves up the cached version > > > > otherwise. > > > > > Dieter Lunnhttp://ubiety.ca > > > > > On Wed, Aug 31, 2011 at 1:12 PM, Josh <josh.m.sha...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > > > > With the release of 3.1, it seems that things have drastically changed > > > > > in the development workflow. > > > > > > With the asset pipeline enabled, and the likes of this in my layouts: > > > > > > = stylesheet_link_tag ''application'', :debug => Rails.env.development? > > > > > = javascript_include_tag ''application'', :debug => > > > > > Rails.env.development? > > > > > > ...every single css, js and image gets re-compiled on every single > > > > > request. This takes forever. > > > > > > My dev log is mostly comprised of this: > > > > > > Started GET "/assets/jquery-ui-1.8.16.custom.css?body=1" for 127.0.0.1 > > > > > at 2011-08-31 14:04:04 -0400 > > > > > Served asset /jquery-ui-1.8.16.custom.css - 304 Not Modified (0ms) > > > > > > It seems to me that the dev rails server (both webrick, and > > > > > passenger), is handling the request of every asset. It didn''t work > > > > > this way in 3.0.x. While it clearly says 304 (0ms) I can attest that > > > > > the overall time to process a page (and all its assets) is > > > > > *significantly* longer. > > > > > > Here''s my application.rb and development.rb - they''re basically the > > > > > 3.1 defaults. > > > > > >http://stackoverflow.com/questions/7248911/rails-3-1-force-developmen. > > > .. > > > > > > So is there a solution here? Even if I didn''t have :debug => true in > > > > > my javascript/stylesheet tag, the JS and CSS files would still have to > > > > > be complied/generated as well as every image - which is still a > > > > > significant regression. > > > > > > -- > > > > > You received this message because you are subscribed to the Google > > > Groups "Ruby on Rails: Talk" group. > > > > > To post to this group, send email to rubyonrails-talk@googlegroups.com > > > . > > > > > To unsubscribe from this group, send email to > > > rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > > > > For more options, visit this group athttp:// > > > groups.google.com/group/rubyonrails-talk?hl=en. > > > > -- > > > You received this message because you are subscribed to the Google Groups > > > "Ruby on Rails: Talk" group. > > > To post to this group, send email to rubyonrails-talk-/JYPxA39Uh4Ykp1iOSErHA@public.gmane.orgm. > > > To unsubscribe from this group, send email to > > > rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > > For more options, visit this group at > > >http://groups.google.com/group/rubyonrails-talk?hl=en.-- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
I found the speed of delivering the page on the production server improved over a week, but a few images still do not server without bringing the building down. Strangely, favicon - yes that piece of sh1t - in the public folder does not get served at all. This file has nothing to do with assets pipeline man. It''s just one of those days.... I am sure there is something missing to it. On Sep 1, 2:14 pm, ad <a...-KzJ8adnBcV2zQB+pC5nmwQ@public.gmane.org> wrote:> You may just move all static assets to public folder. > That would get them loaded without involving asset pipeline. > > Correct me, if I''m wrong. > > On Aug 31, 10:30 pm, Josh <josh.m.sha...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > > > > > > > > That sounds horrible. I''m seeing this occur on every page load, not > > just the first one. > > > On Aug 31, 2:26 pm, Martin Wawrusch <mar...-qs6+VQBngv1Wk0Htik3J/w@public.gmane.org> wrote: > > > > Consider yourself lucky, I had to deal with 5 mins on first load recently. > > > Take a look at the rails-dev-tweaks gem, it helps a lot. In addition to > > > that make sure that you don''t autoload all the models if you use mongoid. > > > > On Wed, Aug 31, 2011 at 11:21 AM, Josh <josh.m.sha...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > > > I understand the difference between dev and prod. > > > > > The issue here is that in 3.0, a dev page load took half a second or > > > > less. It now takes upwards of 5 seconds. > > > > > On Aug 31, 2:15 pm, Dieter Lunn <coder2...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > > > > In development it recompiles with every reload. In production it only > > > > > compiles when the files change and serves up the cached version > > > > > otherwise. > > > > > > Dieter Lunnhttp://ubiety.ca > > > > > > On Wed, Aug 31, 2011 at 1:12 PM, Josh <josh.m.sha...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > > > > > With the release of 3.1, it seems that things have drastically changed > > > > > > in the development workflow. > > > > > > > With the asset pipeline enabled, and the likes of this in my layouts: > > > > > > > = stylesheet_link_tag ''application'', :debug => Rails.env.development? > > > > > > = javascript_include_tag ''application'', :debug => > > > > > > Rails.env.development? > > > > > > > ...every single css, js and image gets re-compiled on every single > > > > > > request. This takes forever. > > > > > > > My dev log is mostly comprised of this: > > > > > > > Started GET "/assets/jquery-ui-1.8.16.custom.css?body=1" for 127.0.0.1 > > > > > > at 2011-08-31 14:04:04 -0400 > > > > > > Served asset /jquery-ui-1.8.16.custom.css - 304 Not Modified (0ms) > > > > > > > It seems to me that the dev rails server (both webrick, and > > > > > > passenger), is handling the request of every asset. It didn''t work > > > > > > this way in 3.0.x. While it clearly says 304 (0ms) I can attest that > > > > > > the overall time to process a page (and all its assets) is > > > > > > *significantly* longer. > > > > > > > Here''s my application.rb and development.rb - they''re basically the > > > > > > 3.1 defaults. > > > > > > >http://stackoverflow.com/questions/7248911/rails-3-1-force-developmen. > > > > .. > > > > > > > So is there a solution here? Even if I didn''t have :debug => true in > > > > > > my javascript/stylesheet tag, the JS and CSS files would still have to > > > > > > be complied/generated as well as every image - which is still a > > > > > > significant regression. > > > > > > > -- > > > > > > You received this message because you are subscribed to the Google > > > > Groups "Ruby on Rails: Talk" group. > > > > > > To post to this group, send email to rubyonrails-talk@googlegroups.com > > > > . > > > > > > To unsubscribe from this group, send email to > > > > rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > > > > > For more options, visit this group athttp:// > > > > groups.google.com/group/rubyonrails-talk?hl=en. > > > > > -- > > > > You received this message because you are subscribed to the Google Groups > > > > "Ruby on Rails: Talk" group. > > > > To post to this group, send email to rubyonrails-talk@googlegroups.com. > > > > To unsubscribe from this group, send email to > > > > rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org > > > > For more options, visit this group at > > > >http://groups.google.com/group/rubyonrails-talk?hl=en.-- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.