Speedup user lookup by also caching if user could not be found #51

wants to merge 1 commit into

1 participant


avoid calling session_serializer.fetch everytime user is called, is also more symetric to the normal user lookup (we do not lookup the userid in the session/change the current user if we already found a user)

This is a nice performance boost for us, since every SessionSerializer.deserialize always hits our database

(Also adds a test for user-caching which did not produce an error when removed)

@grosser grosser closed this Jun 7, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment