diff options
author | antirez <antirez@gmail.com> | 2010-05-07 09:32:26 +0200 |
---|---|---|
committer | antirez <antirez@gmail.com> | 2010-05-07 09:32:26 +0200 |
commit | 8b5bb414f111eeabb0514e686abbc7e0db031221 (patch) | |
tree | 77565e83e9a3165ef22b3a5bfb7803b0b226247c /TODO | |
parent | f424d5f398dde0679ae2afd5063c80d845641a00 (diff) | |
download | redis-8b5bb414f111eeabb0514e686abbc7e0db031221.tar.gz |
Swap file is now locked
Diffstat (limited to 'TODO')
-rw-r--r-- | TODO | 5 |
1 files changed, 1 insertions, 4 deletions
@@ -15,10 +15,7 @@ Virtual Memory sub-TODO: * Check if the page selection algorithm is working well * Divide swappability of objects by refcount * Use multiple open FDs against the VM file, one for thread. -* it should be possible to give the vm-max-memory option in megabyte, gigabyte, ..., just using 2GB, 100MB, and so forth. -* Try to understand what can be moved into I/O threads that currently is instead handled by the main thread. For instance swapping file table scannig to find contiguous page could be a potential candidate (but I'm not convinced it's a good idea, better to improve the algorithm, for instance double the fast forward at every step?). -* Possibly decrRefCount() against swapped objects can be moved into I/O threads, as it's a slow operation against million elements list, and in general consumes CPU time that can be consumed by other threads (and cores). -* EXISTS should avoid loading the object if possible without too make the code too specialized. +* EXISTS should avoid loading the object if possible without making the code too specialized. * vm-min-age <seconds> option * Make sure objects loaded from the VM are specially encoded when possible. * Check what happens performance-wise if instead to create threads again and again the same threads are reused forever. Note: this requires a way to disable this clients in the child, but waiting for empty new jobs queue can be enough. |