Im have a really weird issue, my assets served really slow in development(10 sec per file), thia happens only in Chrome(17.0.963.79). In Firefox all works just fine. My setup: RVM Ruby-1.9.3@p125 Rails 3.2.0 Mac OS 10.7.3 I have tried switch from webrick to mongrel and thin , using rails-dev-tweaks gem , set cache classes to true and false. All this didnt help, im stuck why it's work slow only in chrome and not in firefox? Also this is fresh setup of OS, maybe im missing something, thanks! UPD. If this initial request(e.g. from new tab) all goes smooth. Request take near 2 minute only if im refreshing page. I just can't wrap my head around this issue :(

This seems to have something to do with name resolution. Using (chrome) and localhost:3000/ -- great performance 127.0.0.1:3000/ -- great performance hostname.local:3000/ - Terrible performance as you describe This is unfortunate for me, as I have an alias set up in /etc/hosts to point to 127.0.0.1 that affects how the page gets displayed. So no testing of that in chrome.

ruby-on-railsperformancegoogle-chromeasset-pipeline

Mikhail Nikalyukin

Reputation: 11967

Slow assets ruby 1.9.3, macos, rails 3.2

Im have a really weird issue, my assets served really slow in development(10 sec per file), thia happens only in Chrome(17.0.963.79). In Firefox all works just fine. My setup:

RVM
Ruby-1.9.3@p125
Rails 3.2.0
Mac OS 10.7.3 I have tried switch from webrick to mongrel and thin, using rails-dev-tweaks gem, set cache classes to true and false. All this didnt help, im stuck why it's work slow only in chrome and not in firefox? Also this is fresh setup of OS, maybe im missing something, thanks!

UPD. If this initial request(e.g. from new tab) all goes smooth. Request take near 2 minute only if im refreshing page. I just can't wrap my head around this issue :(

Upvotes: 8

Answers (3)

Dan Williams

Reputation: 3829

We ran into this issue and solved it through using a pow server since it resolves to port 80.

To install pow

curl get.pow.cx | sh

Here is a link to the source for the paranoid.

Hope that helps.

Upvotes: 0

kwerle

Reputation: 2401

This seems to have something to do with name resolution.

Using (chrome) and

localhost:3000/ -- great performance
127.0.0.1:3000/ -- great performance
hostname.local:3000/ - Terrible performance as you describe

This is unfortunate for me, as I have an alias set up in /etc/hosts to point to 127.0.0.1 that affects how the page gets displayed. So no testing of that in chrome.

Upvotes: 8

bsboris

Reputation: 639

I had the same problem. Try setting config.assets.debug = false in development.rb. It helped in my case.

Upvotes: 2

Slow assets ruby 1.9.3, macos, rails 3.2

Answers (3)

Related Questions