Use Redis (Redis2) to store sessions
Bug #855930 reported by
François Marier
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Libravatar (obsolete) |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
Using Postgres to store sessions is usually not a good idea from a performance point of view due to the large amount of writes (and therefore dead rows) that it generates.
From the Postgres slow query log:
2011-09-19 08:57:40 UTC LOG: duration: 519.585 ms statement: UPDATE "django_session" SET "session_data" = E'gAJ9cQF...', "expire_date" = E'2011-10-03 08:57:40.084661' WHERE "django_
Redis2 is not in squeeze, but it's in squeeze backports.
To post a comment you must log in.
Here is Instagram's implementation:
https:/ /gist.github. com/910392
as mentioned on their blog:
http:// instagram- engineering. tumblr. com/post/ 13649370142/ what-powers- instagram- hundreds- of-instances- dozens- of