Our application should continuously write something like 40.000 rows (with 4K data) per seconds (and read 40.000 per second too) continuously.
I have set a TTL to 3 seconds, and we see that when the application stops to write, the amount of object continue growing in the sets for 10 seconds. And it can take up to 40 seconds to erase everything once we have stopped the application.
Is there a way to tell to the evictor to delete more rows at once and start earlier ? The ideal for us is to continuously only have 40.000*3sec rows on the sets.