idea about slave snapshotting option

Hi All,

I mentioned this idea for the windows port, but it may not be a bad
idea for many setups.

The idea is to have 1 master feeding 1 slave.
The master does not persist data to disk, the slave does in-process
SAVEs.
During the slave's in-process SAVE, it would still accept requests and
write CRUD commands to a Q.
After the slave's SAVE was done, it would replay the Q (in their
naturally occurring order).

The benefit this type of architecture has is it does not run the risk
of a COW memory explosion on the slave.
The downside is if the SAVE takes a long time, the Q could get very
big and also use up lots of memory.

I have the feeling (no hard data) that Q-ing commands (which are
delivered @ NIC speed) does not run the same risk of HUGE memory
explosions as COW does, or in other words, the Q-size is more
predictable.

This would be a big win for people running close to their RAM limits
on both master & slave.

Something about the idea seems a bit goofy, so I was wondering if
anyone had feedback on if this would be a good idea or if there is
something about it that makes it just a completely lame idea

- jak