Login and logout flow in Ruby on Rails - Performance & Optimization

Performance: Login and logout flow

MEDIUM IMPACT

This affects page load speed and interaction responsiveness during user authentication.

Handling user login with page reloads

Ruby on Rails

def create
  user = User.find_by(email: params[:email])
  if user&.authenticate(params[:password])
    session[:user_id] = user.id
    respond_to do |format|
      format.turbo_stream { render turbo_stream: turbo_stream.replace('login_form', partial: 'logged_in') }
      format.html { redirect_to root_path }
    end
  else
    flash.now[:alert] = 'Invalid credentials'
    render :new
  end
end

Using Turbo Streams updates only part of the page without full reload, improving responsiveness.

📈 Performance GainNon-blocking partial update reduces interaction delay by 50-70%

Handling user login with page reloads

Ruby on Rails

def create
  user = User.find_by(email: params[:email])
  if user&.authenticate(params[:password])
    session[:user_id] = user.id
    redirect_to root_path
  else
    flash.now[:alert] = 'Invalid credentials'
    render :new
  end
end

Redirect causes full page reload, blocking rendering and delaying interaction readiness.

📉 Performance CostBlocks rendering for 200-500ms depending on network and server response

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Full page reload on login/logout	High (full DOM rebuild)	1+ (full layout)	High (full repaint)	[X] Bad
Partial DOM update with Turbo Streams	Low (targeted DOM changes)	0-1 (localized layout)	Low (partial repaint)	[OK] Good

Rendering Pipeline

Login/logout flows affect the browser's rendering pipeline by triggering network requests, DOM updates, and layout recalculations depending on how the page updates after authentication.

→Network

→Style Calculation

→Layout

→Paint

→Composite

⚠️ BottleneckLayout and Paint stages due to full page reloads and DOM replacements

Core Web Vital Affected

INP

This affects page load speed and interaction responsiveness during user authentication.

Optimization Tips

1Avoid full page reloads on login/logout to reduce blocking rendering.

2Use partial DOM updates (e.g., Turbo Streams) to improve interaction responsiveness.

3Minimize layout shifts by updating only necessary page parts during authentication.

Performance Quiz - 3 Questions

What is the main performance drawback of using full page reloads for login/logout?

A It blocks rendering and causes layout shifts.

B It reduces server load.

C It improves caching efficiency.

D It decreases network requests.

DevTools: Performance

How to check: Record a login or logout action, then analyze the flame chart for long tasks and layout shifts.

What to look for: Look for long blocking times during navigation and large layout or paint events indicating full page reloads.

Practice

1. What does the session[:user_id] typically store in a Rails login flow?

easy

A. The user's email address

B. The ID of the logged-in user

C. The user's password

D. The current time of login

Solution

1. Step 1: Understand session usage in Rails login

   In Rails, session[:user_id] is used to store the unique identifier of the logged-in user to keep track of their session.

2. Step 2: Differentiate from other user data

   Passwords and emails are not stored in session for security and privacy reasons; only the user ID is stored.

3. Final Answer:

   The ID of the logged-in user -> Option B

4. Quick Check:

   session[:user_id] = user ID [OK]

Hint: Session stores user ID, not password or email [OK]

Common Mistakes:

• Thinking session stores password
• Confusing session with cookies
• Assuming session stores full user object

2. Which of the following is the correct way to clear the user session during logout in a Rails controller?

easy

A. reset_session

B. session.clear

C. session[:user_id] = nil

D. session.delete(:user_id)

Solution

1. Step 1: Identify Rails method to reset session

   The reset_session method clears the entire session safely and is the recommended way to log out a user.

2. Step 2: Compare with other options

   While session.delete(:user_id) or setting it to nil removes the user ID, reset_session is more secure as it resets the whole session.

3. Final Answer:

   reset_session -> Option A

4. Quick Check:

   Use reset_session to clear all session data [OK]

Hint: Use reset_session to fully clear session on logout [OK]

Common Mistakes:

• Only deleting user_id but leaving other session data
• Using session.clear, which doesn't regenerate the session ID
• Setting session[:user_id] to nil without resetting session

3. Given this Rails controller code for login:

def create
  user = User.find_by(email: params[:email])
  if user&.authenticate(params[:password])
    session[:user_id] = user.id
    redirect_to dashboard_path
  else
    flash[:alert] = 'Invalid login'
    render :new
  end
end

What happens if the password is incorrect?

medium

A. User is redirected to dashboard

B. User ID is saved in session

C. Application crashes with error

D. Login form is re-rendered with alert

Solution

1. Step 1: Analyze the if condition

   The condition user&.authenticate(params[:password]) returns false if password is wrong, so the else block runs.

2. Step 2: Understand else block behavior

   The else block sets a flash alert and re-renders the login form with render :new.

3. Final Answer:

   Login form is re-rendered with alert -> Option D

4. Quick Check:

   Wrong password triggers else block [OK]

Hint: Wrong password triggers else block with alert [OK]

Common Mistakes:

• Assuming redirect happens on wrong password
• Thinking session is set even if password fails
• Believing app crashes on wrong password

4. Identify the error in this logout action:

def destroy
  session[:user_id] = nil
  redirect_to login_path
end

What is the main issue with this logout method?

medium

A. It does not clear the entire session

B. It redirects to the wrong path

C. It raises a syntax error

D. It does not delete the user record

Solution

1. Step 1: Check session clearing method

   Setting session[:user_id] = nil only removes the user ID but leaves other session data intact.

2. Step 2: Understand best practice for logout

   Best practice is to use reset_session to clear all session data and prevent session fixation attacks.

3. Final Answer:

   It does not clear the entire session -> Option A

4. Quick Check:

   Partial session clearing is insecure [OK]

Hint: Partial session clearing leaves data behind; use reset_session [OK]

Common Mistakes:

• Thinking setting user_id to nil clears session fully
• Ignoring session fixation security risks
• Assuming redirect path affects logout correctness

5. You want to ensure users cannot access the dashboard without logging in. Which code snippet correctly enforces this in a Rails controller using the login session?

hard

A. before_action :require_login

def require_login
redirect_to login_path if session[:user_id].present?
end

B. before_action :require_login

def require_login
redirect_to dashboard_path if session[:user_id].nil?
end

C. before_action :require_login

def require_login
redirect_to login_path unless session[:user_id]
end

D. before_action :require_login

def require_login
redirect_to login_path if session[:user_id] == true
end

Solution

1. Step 1: Understand login check logic

   Users should be redirected to login if session[:user_id] is missing (nil or false).

2. Step 2: Analyze each option's condition

   before_action :require_login def require_login redirect_to login_path unless session[:user_id] end redirects to login unless user_id exists, correctly blocking access. Others have incorrect conditions or redirect to wrong paths.

3. Final Answer:

   before_action :require_login with redirect unless session[:user_id] -> Option C

4. Quick Check:

   Redirect to login if no user_id [OK]

Hint: Redirect unless session[:user_id] exists to block access [OK]

Common Mistakes:

• Using wrong condition logic for session check
• Redirecting to dashboard instead of login
• Checking session[:user_id] == true which is incorrect