You can use SCAN or KEYS to query the keys on the server, to test your idea. Getting the size per key is trickier, but I am to recall that DEBUG OBJECT (which is not really documented and not really intended for use by clients) gives an indicative size. These can be used without requiring the rdb.
However, it wouldn't surprise me if saving it worked fine. This uses fork, which uses (normally) copy-on-write; you don't usually need twice the memory to fork. But i understand your reluctance to risk it with production data.
--
You received this message because you are subscribed to the Google Groups "Redis DB" group.
To unsubscribe from this group and stop receiving emails from it, send an email to redis-db+u...@googlegroups.com.
To post to this group, send email to redi...@googlegroups.com.
Visit this group at https://groups.google.com/group/redis-db.
For more options, visit https://groups.google.com/d/optout.