https://docs.djangoproject.com/en/2.1/topics/cache/#memcached
Particularly the multiple servers section, which does not detail if all memcached daemons should be configured to listen on all interfaces i.e. 0.0.0.0 So just as a sanity check: Scenario 1: (memcached installed naively ( i.e. listening on localhost:11211) on multiple ubuntu servers) * Dev sets up her CACHE_LOCATIONS = ['server1:11211', 'server2:11211'] but is none the wiser that there is no interoperability between servers, meaning roughly 50% cache misses in totality. * Each django process cycles through each location, only localhost is successful, no warning logs generated Scenario 1: (memcached installed and configured to listen on 0.0.0.0:11211) on multiple ubuntu servers) * Dev sets up her CACHE_LOCATIONS = ['server1:11211', 'server2:11211'] and django add/sets keys on all memcache servers successfully * Each django process cycles through each location, adding/setting keys as it goes So, am I right in thinking that the docs assume Scenario 2, but Scenario 1 is a plausible setup, it would just mean lots of misses, but then a pro of no network overhead. Am I missing something? -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/2f487741-4de5-41ed-8c66-7dd565c83948%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
