alexandre-normand commented on PR #1654: URL: https://github.com/apache/iceberg-go/pull/1654#issuecomment-5270776345
> A suggestion that may get you the win sooner: this module already builds on Go 1.26, where stdlib encoding/json/v2 ships with substantial decode-performance improvements and none of the third-party risk. Your benchmark harness is ideally placed to compare it — if it delivers comparable numbers, that's a much easier merge. A quick note on that until I get to the bigger question (I'll follow-up on the other questions later today): Go 1.26 still has `encoding/json/v2` has an experiment and our org doesn't build production images with experiments in most circumstances. Technically, once 1.27 lands, encoding/json will be using `encoding/json/v2` under the hood so no changes would be needed then to get some decent performance improvement. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
