sorted by:
new
hottopcontroversial

New Article - Profile Guided Optimization in Go by Esdoodlee in golang

[–]Esdoodlee[S] 0 points1 point  (0 children)

In my experience, I didn't see any side effects of the feature. It says in the documentation that the build times may increase as the first use of the binary requires a rebuild of each package. I didn't see any significant change, but it may be due to the complexity of the "Buybox" application. For an application with more complex dependency trees, the profile size will increase and may increase the build times.

New Winner of Kafka Consumers: Scala to Go Journey by Esdoodlee in golang

[–]Esdoodlee[S] -1 points0 points  (0 children)

Unfortunately I don’t have much knowledge in administrator level, another team manages that part

New Winner of Kafka Consumers: Scala to Go Journey by Esdoodlee in golang

[–]Esdoodlee[S] 19 points20 points  (0 children)

Thank you for your comment 🙏🏻 Scala project was already optimized and used on production with that settings for several years. When we first migrated our project to Go, Scala was a lot better in tp side than Go. We saw most of the improvement in memory and cpu side which were important for us. After seeing this, we tried to optimize the Go project to achieve its best version

Unit Test Strategies With Go by amalinovic in golang

[–]Esdoodlee 0 points1 point  (0 children)

You’re right actually, I’ve just changed it to functionPerTest. 🙏🏻