The only consequences of losing a session for us is the user getting
delogged. So it is not a big deal.
We have set it up, so that it can save the session data in the db as
backup for when we'll need the system to be more reliable.
--~--~-~--~~~---~--~~
You rece
On 12/18/06, Jeremy Dunck <[EMAIL PROTECTED]> wrote:
> (Off-list)
Well, it was meant to be. :-/
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-use
(Off-list)
On 12/18/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> It's runing purely off memcached. We have at least 6 memcached servers,
> maybe a few more, and it just updates memcached when the session
> updates.
This didn't really answer whether volatile session data is OK.
Are you a
It's runing purely off memcached. We have at least 6 memcached servers,
maybe a few more, and it just updates memcached when the session
updates.
On Dec 18, 4:42 am, "Jeremy Dunck" <[EMAIL PROTECTED]> wrote:
> On 12/17/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> > We also redid the sessi
On 12/17/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> We also redid the session system to run completely off memcached, as
> this was the real killer for the database.
I guess volatile session data is OK, or do you write out sessions from
memcached to disk at intervals?
I'm going to have a
Thought I'd give everyone an update. We're struggling to stop Django
from doing some queries in templates/context procs that we're missing,
but we've nearly got the SQL load completely stable (although we're
still having some random issues).
We also redid the session system to run completely off
Yes we use memcached
On Dec 11, 4:13 am, "João Cruz Morais" <[EMAIL PROTECTED]> wrote:
> are you using some sort of cache server such as memcache?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" gro
7 matches
Mail list logo
