Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Rex Dri Rex Dri
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 33
    • Issues 33
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

Rappel : l'instance GitLab de l'UTC n'est pas destinée au stockage de fichiers volumineux (images/vidéos/documents). Pensez également à ne pas pousser avec votre code les dépendances ou résultats des builds/exécutions (préférer la génération d'artifacts par la CI). Merci.

  • Rex Dri
  • Rex DriRex Dri
  • Issues
  • #54
Closed
Open
Issue created Feb 24, 2019 by Florent Chehab@chehabflOwner

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 and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking