During high-performance testing, contention was observed on a global mutex controlling the assignment of transaction numbers and the values of certain transaction state variables that are used by threads other than the owning thread. Logic that cleans up user/file-specific state variables and updates certain file state variables is typically called with this mutex held, which can be quite frequent under heavy loads. This mutex is no longer held during these calls. Further, portions of the logic in this call are now skipped when the function is later called for overall performance gains.