PDA

View Full Version : Ruby on Rails Slow to Show Updates


shellerik
09-22-2008, 01:05 PM
When I make a change to my rails app I don't see the change right away when loading my site in a browser. I haven't figured out exactly how long the lag time is yet, maybe a couple hours.

At first I thought it was something special about changes to config/environment.rb but now I see that I can even delete methods from a controller and save the file and they will still load!

I'm trying to fix some problems with my layouts not rendering correctly but it is hard to test if I don't know whether my latest changes have made an impact yet. Is this a server-side caching problem? How do I get my changes to have an immediate affect?
shellerik
09-25-2008, 11:15 AM
This problem went away for a few days and now it is back. I have a ticket open but I don't get the feeling they're even reading what I'm writing... Has anyone else experienced this problem where changes you make to your site take hours to show up, as if an old, cached version of your site is being served up?
Early Out
09-25-2008, 12:08 PM
Tickets often get very slow responses - use Live Chat, instead.

As far as I know, BH doesn't do any caching at all. If old pages are being cached, it's happening either on your PC, or at your ISP's head end (some ISP's cache pages as a misguided means of providing faster response).
shellerik
09-25-2008, 01:35 PM
I am able to use my web app to update content in my database and view the new content but it's still calling old code that I replaced several hours ago. If there is no caching could it be that my site is being served up from multiple servers and the changes haven't propagated?

I don't see live chat in the helpdesk, forum, or control panel. Where do I find that?
Early Out
09-25-2008, 02:07 PM
Live Chat - big blue button on the main bluehost.com page.

As far as I know, no one's stuff is hosted on more than one server.
shellerik
09-25-2008, 05:18 PM
The live chat person recommended reinstalling my gems. Since the problem has mysteriously gone away for now I'll have to wait for it to reoccur before I try that. I also found this page http://tom.wilcoxen.org/2005/07/ where in the comments some people recommend killing dispatch.fcgi jobs with the theory that new ones would load and pickup any changed files.