We upgraded to 4.1.17 from 4.0.92 and we are seeing heavy increase in the data size on disk. DBPrintLog reports massive amounts of DBINs and DINs. A cursor walk of the database checking for number of duplicates for each key, shows that the data actually does not contain that many duplicates.
I know we had this conversation about duplicates in 4.x
10285528
Is the increase because we have the duplicate tree for all keys in 4.1.17, immaterial of whether or not they actually have duplicate values?
Any idea what's going on here? Any help to go about debugging this is greatly appreciated.
PS : I will get the DBPrintLog output in a while.
-Vinoth