Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>It sounds like you want Memcached to behave like normal RAM and page to disk when it is full. It doesn't by default, but you can imitate it by writing your own cache backend as @AlexanderAfanasiev mentioned. The implementation would be something along these lines:</p> <p>First, define three caches:</p> <pre><code>CACHES = { 'default': { 'BACKEND': 'myapp.cache.DoubleCache', }, 'memcached': { 'BACKEND': 'django.core.cache.backends.memcached.MemcachedCache', 'LOCATION': '127.0.0.1:11211', }, 'filecache': { 'BACKEND': 'django.core.cache.backends.filebased.FileBasedCache', 'LOCATION': '/foo/bar', } } </code></pre> <p>Then, in myapp/cache.py:</p> <pre><code>from django.core.cache.backends.base import BaseCache from django.core.cache import get_cache, cache mem_cache = get_cache('memcached') file_cache = get_cache('filecache') class DoubleCache(BaseCache): def get(self, key, default=None, version=None): result = mem_cache.get(key, default=default, version=version) if result: return result else: return file_cache.get(key, default=default, version=version) def set(self, key, value, timeout=None, version=None, client=None, _add_only=False): memcache_result = mem_cache.set(key, value, timeout=timeout, version=version, client=client, _add_only=_add_only) file_result = file_cache.set(key, value, timeout=timeout, version=version, client=client, _add_only=_add_only) return memcache_result </code></pre> <p>This will always store values in both caches. It will retrieve values from Memcached, and if it misses, will try the file_cache. That means that Memcached can manage its own roll-off and only the oldest hits will have to fall back to file_cache. This is what you'd want.</p> <p>Of course, you'll also have to implement the rest of the cache functions like <code>delete()</code>, <code>get_many()</code>, etc. Hopefully this gets you on the right path.</p>
    singulars
    1. This table or related slice is empty.
    1. PODjango Cache: Use Memcached and fallback to FileSystem
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USkrimkus
    1. USkrimkus
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PODjango Cache: Use Memcached and fallback to FileSystem
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTBountyClose
    1. COTnx for the detailed answer, however won't the set() method will always succeed to store the value in memcahed? it will just drop an older value and store the new one, causing the get method to never reach the file_cache. Correct me if I'm wrong.
      singulars
      1. PO
      1. USYardenST
    2. COYes, set() will store in both. But if memcached fills up (which will happen with 1GB of ram and a 2GB dataset), then half the values will be in both and half will only be in the file_cache. As memcached drops the least used if it fills up, the half in the file_cache will be the least used pages. That's what you want. If you then try to do a get on a page that is rarely used, it will miss on the memcached get and then return the file_cache one.
      singulars
      1. PO
      1. USkrimkus
    3. COI get it now, I'll try it later to see if it works as expected
      singulars
      1. PO
      1. USYardenST
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload