- Sort Score
- Result 10 results
- Languages All
Results 1 - 3 of 3 for Overhead (0.19 sec)
-
doc/next/5-toolchain.md
## Compiler {#compiler} The build time overhead to building with [Profile Guided Optimization](/doc/pgo) has been reduced significantly. Previously, large builds could see 100%+ build time increase from enabling PGO. In Go 1.23, overhead should be in the single digit percentages. ## Assembler {#assembler}
Plain Text - Registered: Tue May 07 11:14:38 GMT 2024 - Last Modified: Thu Apr 18 15:39:17 GMT 2024 - 332 bytes - Viewed (0) -
doc/go_mem.html
<p> it can happen that <code>g</code> prints <code>2</code> and then <code>0</code>. </p> <p> This fact invalidates a few common idioms. </p> <p> Double-checked locking is an attempt to avoid the overhead of synchronization. For example, the <code>twoprint</code> program might be incorrectly written as: </p> <pre> var a string var done bool func setup() { a = "hello, world" done = true
HTML - Registered: Tue May 07 11:14:38 GMT 2024 - Last Modified: Mon Mar 04 15:54:42 GMT 2024 - 26.6K bytes - Viewed (0) -
doc/godebug.md
setting](/pkg/crypto/tls/#ConnectionState.ExportKeyingMaterial). Go 1.22 changed how the runtime interacts with transparent huge pages on Linux. In particular, a common default Linux kernel configuration can result in significant memory overheads, and Go 1.22 no longer works around this default. To work around this issue without adjusting kernel settings, transparent huge pages can be disabled for Go memory with the
Plain Text - Registered: Tue May 07 11:14:38 GMT 2024 - Last Modified: Tue Apr 16 17:29:58 GMT 2024 - 13.5K bytes - Viewed (0)