[GH-ISSUE #98] document using a more scalable session store - memcached? #96

New issue

Closed

opened 2026-02-26 09:35:35 +03:00 by kerem · 1 comment

kerem commented

2026-02-26 09:35:35 +03:00

Owner

Originally created by @ThomasWaldmann on GitHub (Nov 30, 2013).
Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/98

by default, django stores sessions into the database, which might be an issue for a heavily used site.

note: we can NOT use cookie sessions as we need to be able to access the session store on the server, to update detected ipv4/v6 addresses.

it can be optimized using memcached, see the django docs.

document (in our docs) how to do it (point to django docs?).

Originally created by @ThomasWaldmann on GitHub (Nov 30, 2013). Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/98 by default, django stores sessions into the database, which might be an issue for a heavily used site. note: we can NOT use cookie sessions as we need to be able to access the session store on the server, to update detected ipv4/v6 addresses. it can be optimized using memcached, see the django docs. document (in our docs) how to do it (point to django docs?).

kerem

2026-02-26 09:35:35 +03:00

closed this issue
added the
enhancement

task

scalability
labels

kerem commented

2026-02-26 09:35:36 +03:00

Author

Owner

@ThomasWaldmann commented on GitHub (Oct 27, 2014):

I didn't see any load issue due to this yet, so we can close this for now and reopen in case it really happens to be a problem.

@ThomasWaldmann commented on GitHub (Oct 27, 2014): I didn't see any load issue due to this yet, so we can close this for now and reopen in case it really happens to be a problem.