4

my apps views are taking anywhere from 800-2000ms to load according to the logs.

I noticed for a page w/o accessing current_user the time is under 10ms... Anytime current_user is accessed it takes 400ms just to get current_user.

Any ideas why it is taking so long to get the current_user? Any way to track down where the lag is in performance?

Thanks

AnApprentice
  • 108,152
  • 195
  • 629
  • 1,012
  • Sounds like it could be a database-related issue, or possibly some kind of middleware that's misbehaving. – Seth Sep 20 '11 at 23:06
  • 4
    Look at the log file to see the SQL statement executed. You might have to add an index based on how the user object is queried while trying to construct the current user. – Harish Shetty Sep 21 '11 at 00:23
  • Any before_filters that could be timing out? This can be file system corruption as well. Check your volume's file system. – jschorr Sep 21 '11 at 03:02
  • You might also check `User.find(x)` to if the delay only comes from the `current_user` method. – RobinGower Sep 21 '11 at 22:20
  • Very strange but it turned out that we were on rails 3.0.5 and moving to rails 3.0.9 fixed this. It was also only the user table casuing the issue. not sure why. – AnApprentice Sep 21 '11 at 22:29

1 Answers1

0

The logs should show you the database times as well as the render times. See if they track. i.e. high render times always implies a high database time.

There are various ways to profile rails if it is not a database issue.

The Railscasts #98 Request Profiling episode is old but it is a sample of what Rails has already built in for such questions.

pedz
  • 2,271
  • 1
  • 17
  • 20