Using a Bitcoin-Qt v0.16.0 ([downloaded from bitcoin page](https://bitcoin.org/bin/bitcoin-core-0.16.0/bitcoin-0.16.0-osx.dmg)) in an macOS High Sierra 10.13.4 

When I start after a fresh install Bitcoin-Qt as a mainnet node and wallet, the wallet prompt that about 203gb is going to be used in my disk
![image](https://user-images.githubusercontent.com/20187136/39899688-ba820bfe-5493-11e8-87d9-460ed5716a02.png)

When I start the node and wallet as testnet, shows the same message about the 203gb disk usage
![image](https://user-images.githubusercontent.com/20187136/39899756-17b31214-5494-11e8-8a57-60e604e74afb.png)

It seems that the second time the message is wrong, due that the testnet database uses about 14gb.
consensus.powLimit = uint256S("00000000ffffffffffffffffffffffffffffffffffffffffffffffffffffffff");
        consensus.nPowTargetTimespan = 14 * 24 * 60 * 60; 
        consensus.nPowTargetSpacing = 10 * 60;
        consensus.fPowAllowMinDifficultyBlocks = false;
        consensus.fPowNoRetargeting = false;
        consensus.nRuleChangeActivationThreshold = 1916; 
        consensus.nMinerConfirmationWindow = 2016; 
        consensus.vDeployments[Consensus::DEPLOYMENT_TESTDUMMY].bit = 28;
        consensus.vDeployments[Consensus::DEPLOYMENT_TESTDUMMY].nStartTime = 1199145601; 
        consensus.vDeployments[Consensus::DEPLOYMENT_TESTDUMMY].nTimeout = 1230767999; 
        
        consensus.vDeployments[Consensus::DEPLOYMENT_CSV].bit = 0;
        consensus.vDeployments[Consensus::DEPLOYMENT_CSV].nStartTime = 1462060800; 
        consensus.vDeployments[Consensus::DEPLOYMENT_CSV].nTimeout = 1493596800; 
        
        consensus.vDeployments[Consensus::DEPLOYMENT_SEGWIT].bit = 1;
        consensus.vDeployments[Consensus::DEPLOYMENT_SEGWIT].nStartTime = 1479168000; 
        consensus.vDeployments[Consensus::DEPLOYMENT_SEGWIT].nTimeout = 1510704000; 
        
        consensus.nMinimumChainWork = uint256S("0x0000000000000000000000000000000000000000028822fef1c230963535a90d");
        
        consensus.defaultAssumeValid = uint256S("0x0000000000000000002e63058c023a9a1de233554f28c7b21380b6c9003f36a8"); 
        /**
         * The message start string is designed to be unlikely to occur in normal data.
         * The characters are rarely used upper ASCII, not valid as UTF-8, and produce
         * a large 32-bit integer with any alignment.
         */
        pchMessageStart[0] = 0xf9;
        pchMessageStart[1] = 0xbe;
        pchMessageStart[2] = 0xb4;