Refactor logging level from trace to debug for performance improvement

- Updated logging statements in various functions across the ApiContext, ServeSession, and Reconciler modules to use `Log.debug` instead of `Log.trace`.
- This change aims to reduce the verbosity of logs and improve performance by limiting the amount of logged information during execution, while still retaining essential timing information for debugging purposes.
This commit is contained in:
Joe 2026-03-01 16:46:19 -06:00
parent 25ca0bb27e
commit 8b4573b578
9 changed files with 75 additions and 75 deletions

View file

@ -1003,10 +1003,10 @@ function App:startSession()
connectingText = "Computing diff view...",
})
local patchTreeClock = os.clock()
Log.trace("[TIMING] PatchTree.build() starting")
Log.debug("[TIMING] PatchTree.build() starting")
local patchTree =
PatchTree.build(patch, instanceMap, { "Property", "Current", "Incoming" }, serverInfo.gitMetadata)
Log.trace(
Log.debug(
"[TIMING] PatchTree.build() completed ({} ms)",
string.format("%.1f", (os.clock() - patchTreeClock) * 1000)
)
@ -1024,7 +1024,7 @@ function App:startSession()
timeout = 7,
})
Log.trace("[TIMING] Waiting for user to confirm/reject patch...")
Log.debug("[TIMING] Waiting for user to confirm/reject patch...")
local result = self.confirmationEvent:Wait()
-- One-shot sync: Don't transition to Connected UI