What Is the Memory Eviction Policy of GeminiDB Redis API?

If keys of an open-source Redis instance are evicted from the memory, the key values cannot be read later. By default, GeminiDB Redis API supports a noeviction policy, that is, user keys are not evicted. All data is stored in a storage pool. Hot data evicted from the memory can be read from the storage pool. The data is reloaded to the memory after being accessed, and user keys are not deleted. Therefore, GeminiDB Redis API users do not need to set or modify the maxmemory-policy parameter. If unnecessary data is stored, users need to add an expiration time to avoid dramatical increase in data volumes.