4 WARNING: are you a possible Redis contributor?
5 Before implementing what is listed what is listed in this file
6 please drop a message in the Redis google group or chat with
7 antirez or pietern on irc.freenode.org #redis to check if the work
8 is already in progress and if the feature is still interesting for
9 us, and *how* exactly this can be implemented to have good changes
10 of a merge. Otherwise it is probably wasted work! Thank you
15 * Use multiple open FDs against the VM file, one for thread.
16 * Check what happens performance-wise if instead of creating 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.
18 * Use just a single IO Job to swap out a key, and add a mutex so that pages in the page table can be marked as used and scanned from the thread itself.
23 * PING between master and slave from time to time, so we can subject the
24 master-slave link to timeout, and detect when the connection is gone even
25 if the socket is still up.
30 * SORT: Don't copy the list into a vector when BY argument is constant.
31 * Write the hash table size of every db in the dump, so that Redis can resize the hash table just one time when loading a big DB.
32 * Read-only mode for slaves.
37 * What happens in the following scenario:
38 1) We are reading an AOF file.
41 What happens if between 1 and 2 for some reason (system under huge load
42 or alike) too many time passes? We should prevent expires while the