Particularly, since data-in-memory is false, are you comparing Redis memory usage to Aerospike disk usage?
If you are comparing memory then since these aren’t in memory, you must be comparing Aerospike’s various static allocations that support clustering/fabric/etc and the 64 bytes per record in the primary index. Aerospike does pre-allocate a fair amount of memory for various internal tasks but this isn’t an issue for most deployments since we don’t really target tiny data-sets like Redis; if the amount of pre-allocated RAM is an issue we can help you configure some of that down.