Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Rex Dri
Rex Dri
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 32
    • Issues 32
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Rex Dri
  • Rex DriRex Dri
  • Issues
  • #54

Closed
Open
Opened Feb 24, 2019 by Florent Chehab@chehabfl
  • Report abuse
  • New issue
Report abuse New issue

Performance optimization with request.user

The user from the request class in Django is used in multiple locations. It seems that this result in an outrageous number of requests to the DB.

We need to look into storing all the user attribute in the request and making use of these new attributes through the backend to optimize performance a bit.

To upload designs, you'll need to enable LFS. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
3
Labels
backend enhancement performance
Assign labels
  • View project labels
Reference: rex-dri/rex-dri#54