Evaluate performance impact of debugTransaction()

There's a way to tag certain transactions as debug transactions and have the system track the lifetime of that transaction. This collects fine grained information about the tagged transaction and writes it to the trace file. This is very useful to debug correctness and performance issues and can possibly be a building block to provide better visibility into the database.

We need to evaluate the performance impact of enabling this for all transactions and see if it's a viable option. Evaluate the impact with and without writing it to a file.