Home/ Questions/Q 3281978
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-17T19:52:34+00:00

I am scratching my head over for this issue for last few weeks. My

  • 0

I am scratching my head over for this issue for last few weeks.

My local rails dev environment has been so slow for some reasons. I have production environment working as quick as a bullet on the servers. But with the same code, my dev environment is taking so slow and I have decided to dig into that further.

I have found that the problem exists with two of my main models. I could identify it with Console in the terminal.

Admin.last 
#(super quick, no records there)
Club.last 
#(super quick, about 1400 records there)

User.last 
#(super slow, about 3 seconds. but no records in there yet!!!!)
Site.last 
#(super slow,about 3 seconds, too.. but this one has about 4000 records)

Admin and User has almost the same number and type of fields except User has a photo (using Paperclip). But paperclip is working fine with Club anyway.

Any help will be appreciated.

Thanks.

EDIT: I have found more precise issue there. In both User and Site models, I have this reference which is slowing things down on my dev env.

include ActionController::UrlWriter

I know we should not use URL in the model level. But I have to use it. The question now is why the heck it’s slow to use it only on Dev env, not on production?
Thanks.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    In the development environment code is reloaded after each request and not cached. This means you can make changes to the code and just refresh the page and not have to refresh the server.

    In production mode routes/models are cached as these are less likely to be edited between requests without a server restart.

    • 0