http://blogs.technet.com/exchange/archive/2006/03/10/421742.aspxThe msExchESEParamLogBuffers storage group attribute governs the number of Extensible Storage Engine (ESE) log buffers that are used by the Exchange information store. ESE uses a set of log buffers to hold information in RAM before it writes to the transactionen-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.technet.com/exchange/archive/2006/03/10/421742.aspx#421814Sat, 11 Mar 2006 16:15:48 GMTd5e57398-b9ef-4490-9955-07cbb4e4a80d:421814subject: exchange <br>Research In Motion and NTP Sign Definitive Settlement Agreement to End Litigation <br>RIM Announces Availability...http://blogs.technet.com/exchange/archive/2006/03/10/421742.aspx#421919Mon, 13 Mar 2006 20:54:47 GMTd5e57398-b9ef-4490-9955-07cbb4e4a80d:421919Teo HerasTwo part question: <br>1. Based on your comment &quot;Another good reason for the increase (and why it should be done for a configuration step as part of a server install).&quot; Should this configuration be included when building a new server. &nbsp;One that will hold 4,000 mailboxes for example? &nbsp;Or, should we only add it if we see log stalling behaviour when we run JetStress to validate the storage? &nbsp; <br> <br>2. &nbsp;As long as we're on the subject of cache sizes, what about the value of msExchESEParamCacheSizeMax. &nbsp;In articles I've read, this value should not be changed in Exchange 2000 unless there are performance issues. &nbsp;With Exchange 2003 this value appears to be a standard configuration on servers with more than 3GB of memory and should be set to 311296. <br> <br>Thank you, <br> <br>Teo <br> <br>