Add note to restart redis after `vm.overcommit_memory` changes

Redis needs to be restarted after a sysctl `vm.overcommit_memory` change to take effect.

I ran into this problem yesterday with @andrewgross, and it took us a long time to realize that months ago, when sysctl was changed, Redis was running and wasn't restarted after the change.