In http://blog.c7solutions.com/2012/08/how-speed-up-transport-logging.html I discuss how to speed up the interval between events happening and the log file being written to the disk for lab and testing scenarios. This is a quick update to that article to mention that in Exchange 2013 the following files can be edited to speed up log commit to disk for each of the Exchange 2013 transport services:
EdgeTransport.exe.config (for Transport service logs)
MSExchangeDelivery.exe.config (for Mailbox Transport Delivery service logs)
MSExchangeSubmission.exe.config (for Mailbox Transport Submission service logs)
MSExchangeFrontEndTransport.exe.config (for Frontend Transport service logs)
To reduce the memory cache time to 30 seconds set the following two entries in the above listed files (found in \Program Files\Microsoft\Exchange Server\v15\bin) within the AppSettings area:
<add key="SmtpSendLogFlushInterval" value="0:00:30" />
<add key="SmtpRecvLogFlushInterval" value="0:00:30" />
The two values above control different log files. Each transport log file has a different setting – so its possible to set Receive Connector protocol logging to a different value from Send Connector protocol logging if you wanted to. Once you make your changes to Edge.Transport.exe.config you need to restart the relevant service for the changes to be picked up.
Here is a list of the properties that I know about that can be changed:
- SmtpSendLogFlushInterval – Timespan value on how often to write the Send Connector protocol logging log to disk
- SmtpRecvLogFlushInterval – Timespan value on how often to write the Receive Connector protocol logging log to disk
- ConnectivityLogFlushInterval – Timespan value on how often the Connectivity log is written to disk.
In addition to the above, which are all timespan values for how often to write to disk, if the memory buffer that contains the log entries fills up then it will be written to disk as well. The default memory buffers are 1MB. So on a very busy server you might find that the log writing is not every five minutes exactly but of a more “random” nature as the buffer is filled. The following settings control the size of the buffer for the above timespans: