sanjeet006py

> @sanjeet006py Using nanoseconds resolution for measuring calls which themselves take less than 1ms adds considerable measurement overhead. AFAIK each call to System.nanosecond itself takes ~25- 30ns so for 2...

> Have you looked at the time taken by the execution of mutationPlan for upsert select on a table which has large number of rows and client side deletes which...

@tkhurana based on the response in [here](https://github.com/apache/phoenix/pull/2061#issuecomment-2617799789), please let me know if there is a concern with the overall change in this PR. Thanks

> IMO we don't need to track at further granularity. Just track time taken by a single `executeMutation` call. You can use nano seconds granularity for it. @tkhurana Recently, we...

> @sanjeet006py Majority of times the time to create mutationPlan is so insignificant that this metric won't be useful. The only time you are interested in this metric is when...

> 1 ms was important for a huge time taken? How huge was the huge time? Extra 1ms was spent in every `executeUpdate()` call and a user was trying to...