[Csync2] csync2 db asymetry

[Art -kwaak- van Breemen]

Hello,

On Fri, Dec 19, 2008 at 10:28:26AM +0100, Vincent Régnard wrote:
> If the difference has to do with compression or history, why is it
> always bigger on the same side (master) and not randomly bigger one side
> and also the other ?

It's pretty normal for a master database to be bigger than the
slave. The reason is that the master usually does more
transactions, and hence is more fragmented. The slack will
increase due to that, and since sqlite stores everything in a
single file, the fragmentation difference is very large.
After a dump/restore  or a full vacuum, the databases should be
about equal size.

The master touches:
- hints
- dirty
- file

The slave touches:
- file

With postgres replication we even see a file size difference of 10 to 50%
of the master. (We actually have database size differences of 10G and then
we are not talking 50%, but less ;-) ).
-- 
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in email?