Jens Frank wrote:
Currently we generate 1GB of mysql redo log per 10
hours, that's about
300 kbit/s or 72GB/Month. This is without using compression, which would
save some 50% of the above figures.
1.5 will reduce the binlog sizes somewhat. In 1.4, the bulk data is
handled twice: it's saved into cur, then later loaded out of cur,
gzipped and and saved into old. In any case, 72 GB/month is hardly a
"huge sucking sound" on bandwidth, last month we sent 22 TB out of Florida.
-- Tim Starling