authenticated user alwayse fetch from database for each request

[anonymous]

even set the SESSION_ENGINE='django.contrib.sessions.backends.cache' or cache_db, and user has login, request.user is still always need to fetch from db for each request . and user groups, permissions will also need to fetch again when use. It takes too many cpu clocks.

why not save the authenticated user in session. a little things should to do is update the user in session when user object or user permissions or groups has changed.

[Russell Keith-Magee]

An interesting idea, but I don't think it's as simple as you make out. There are all sorts of cache invalidation issues hiding underneath this.

I am also highly skeptical that reloading the user, groups and permissions is a bottleneck in your application. I don't doubt that this *could* be optimized, but I find it hard to believe that this is the biggest performance improvement available to your (or any) project.

Marking wontfix for now, but willing to entertain discussion if someone is particularly enthused by the idea.