zuston commented on PR #2206: URL: https://github.com/apache/fluss/pull/2206#issuecomment-3674027724
> A better approach would be to move the flushLatencyHistogram into RocksDBWriteBatchWrapper and update it directly within RocksDBWriteBatchWrapper#flush. This ensures accurate, per-flush latency tracking. Make sense. Let me follow your idea. thanks @wuchong -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
