Under committed access, note the following memory considerations:
Essbase retains redundant data until a transaction commits. Allow disk space for double the size of the database to accommodate redundant data.
Models with a large number of blocks may experience memory problems under committed access. Each lock (one lock per block) uses approximately 80 bytes of memory per calculation, and each lock is held in memory until the transaction is complete. There is a limit to the addressable memory space per process, and eventually models with a large number of blocks may hit this limit, causing the transaction to terminate. In such cases, consider using Uncommitted Access.