Skip to Main Content

Berkeley DB Family

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

space utilization with 5.0.103

user4173612Mar 22 2014 — edited Mar 24 2014

We recently upgraded from 4.1.27 to 5.0.103 and are seeing some space utilization problems.  We have a DB environment that contains 7 Databases.  This data is updated once an hour by a batch process that runs for a few minutes and then is read only for rest of the time.  We have a staging environment where we are running 5.0.103 and a production environment still running 4.1.27.  The data in both is the same.  The 4.1.27 environment occupies 51G of disk space.  When I run the DbSpace utility it shows:

  FileSize (KB)  % Used

--------  ---------  ------

TOTALS52486001  49

In contrast the 5.0.103 environment occupies 163G and the DbSpace utility shows:

  FileSize (KB)  % Used

--------  ---------  ------

TOTALS   169471834  23

To gather some statistics I stopped the 5.0.103 environment, restarted and ran a task to capture some EnvironmentStats. No other processes were running so no updates or reads.  Here are some of the stats:
cleanerBackLog 120

lastKnownUtilization 60

nBINDeltasCleaned 20058

nCleanerDeletions 28

nCleanerEntriesRead 383665

nCleanerProbeRuns 0

nCleanerRuns 31

An hour later:

cleanerBackLog 122

lastKnownUtilization 60

nBINDeltasCleaned 138440

nCleanerDeletions 184

nCleanerEntriesRead 2388887

nCleanerProbeRuns 0

nCleanerRuns 187

The disk used is now 165G and DbSpace shows:

  FileSize (KB)  % Used

--------  ---------  ------

TOTALS   173304217  22

So after the cleaner running by itself for an hour we seem to have less utilization.  Here are my environment settings:

CacheMode: null

CacheModeStrategy: null

CachePercent: 30

CacheSize: 9019431321

EnvironmentConfig: allowCreate=true

cacheSize=9019431321

txnNoSync=false

txnWriteNoSync=false

{je.env.runCleaner=true, je.log.fileMax=1073741824, je.evictor.nodesPerScan=100, je.log.totalBufferBytes=4194304, je.evictor.lruOnly=false, je.cleaner.minUtilization=60, je.cleaner.threads=3, je.env.isTransactional=false, je.env.isReadOnly=false, je.maxMemoryPercent=30, je.log.faultReadSize=786432, je.log.bufferSize=1048576, je.lock.nLockTables=19, je.log.numBuffers=4, je.log.iteratorReadSize=32768}

Have I misconfigured something so bad as to cause this or is it an issue with 5.0.103 that did not exist in 4.1.27?

Thanks,

Chris

Comments

Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on Apr 21 2014
Added on Mar 22 2014
7 comments
3,043 views