TRANSITIONING TO GO SEP 20 2023 Robert Pająk pellared @ GitHub SplunkHello whoami fundamentals going further more, more q&a 01 02 03 04 05whoamiROBERT PAJĄK Go maintainer Go language committee Tour of Go 2. Read and try: How to Write Go Code 3. Read and follow: Effective Go 4. Read and follow: CodeReviewComments 5. Check: Go by Examplehttps://go.dev/tourhttps://go.dev/doc/codehttps://go.dev com/golang/go/wiki/CodeReviewCommentshttps://gobyexample.comgoing furtherhttps://www.gopl.iohttps://go.dev/ref/memhttps://exercism.orghttps://quii.gitbook.io/learn-go-with-testshttps://go101.orghttps://go.dev/blogmore

Go in TiDB 申砾@PingCAP Agenda • About Me • What is TiDB • TiDB Architecture • SQL Layer Internal • Golang in TiDB • Next Step of TiDB About Me • Shen Li (申砾) • Tech Lead of TiDB, VP of Engineering Why Go? • Productivity • Concurrency • Great for network programming • GC • Standard libraries && Tools • Good performance • Quick improvement Go in TiDB • More than 100k lines of Go code and session is hard • Account for large memory allocation • Account for memory consuming operators New in Go1.8 • Better GC • Pauses 50μs • sort.Slice Next Step of TiDB • Switch to gRPC • Document support

Go compile time instrumentation Przemysław Delewski February 18, 2025 Warsaw, PolandAgenda 1. Short bio 2. Observability domain 3. OpenTelemetry 4. History of OpenTelemetry go compile time instrumentation I’m also founding member of the OpenTelemetry Go compile-time instrumentation project https://github.com/open-telemetry/community/blo b/main/projects/go-compile-instrumentation.mdSoftware complexity spanHistory of OpenTelemetry go instrumentationBeginnings of go instrumentation Everything started with two proposals: - https://github.com/open-telemetry/opentelemetry-go-instrumen tation/issues/3

Go Practices in TiDB 姚维 PingCAP wink@pingcap.com Agenda ● How to build a stable database ○ Schrodinger-test platform ○ Failpoint injection ○ Goroutine-leak detection ● Optimization ○ Chunk vs interface{} errors.New("mock commit error") // } …. } https://github.com/pingcap/tidb/blob/master/store/tikv/txn.go#L223 The generated gofail code func (txn *tikvTxn) Commit(ctx context.Context) error { if vmockCommitError or: __fp_mockCommitError.BadType(vmockCommitError, "bool"); }; …. } $ gofail enable store/tikv/txn.go Why we need a new failpoint ● Generated code is not readable ● Concurrent testing will use the same

Go runtime related problems in TiDB production environment About me ● Arthur Mao(毛康力), Senior Engineer@PingCAP ● TiDB core developer (top3 contributor) ● GitBook about golang internals (@tiancaiamao) consider priority ● CPU dense workload could affect IO latency Conclusion Part II - Memory control ● Go Runtime ○ Allocated from OS (mmaped) ○ Managed Memory ■ Should the memory be returned to the OS? ○ memory footprint is abnormal ● The memory available on this node is not too much Description ● The Go Runtime thinks it does not use much memory ● The OS does not release the memory (RSS is high) Investigate

to do it well Jakub Daligapart 0: who am IGolang Warsaw #12 (29.06.2017) Jakub Daliga - GraphQL w Go (PL)notable experience ~9 years of professional programming 6 companies smallest: 3 people largest: could go wrong?part 2: practical TODO liststep 1: what is the emotion you want for your audience?step 2: generate a title 1. "Getting Started with Go: A Beginner's Guide" 2. "Concurrency in Go: Mastering Microservices with Go" 4. "Effective Error Handling in Go: Best Practices and Patterns" 5. "The Power of Go Modules: Dependency Management Simplified" 6. "Optimizing Performance in Go Applications" 7

problem. May 2014: I go to C++Now for the first time.FIRST, AN ORIGIN STORY (and timeline of sorts) Mid 2013: I start playing with monadic futures. I run into a problem. May 2014: I go to C++Now for the 2015: I go back to C++Now and tell folks about the problem.FIRST, AN ORIGIN STORY (and timeline of sorts) Mid 2013: I start playing with monadic futures. I run into a problem. May 2014: I go to C++Now C++Now for the first time. May 2015: I go back to C++Now and tell folks about the problem. September 2017: I talk to Gašper Ažman at CppCon.FIRST, AN ORIGIN STORY (and timeline of sorts) Mid 2013: I start

be more efficient so you go get some beerexploit nicheprofiler knows where code is inefficient exploit niche I figured out where your code could be more efficient so you go get some beerprofiler knows efficient so you go get some beer profiler knows why code is inefficient exploit nicheprofiler knows where code is inefficient I figured out where your code could be more efficient so you go get some beer of time in interpreter exploit nicheI figured out where your code could be more efficient so you go get some beer lots of time in interpreter ⇒ use native libraries exploit niche profiler knows where

This document is filled with user, usage and revenue charts that go up-and-to-the-right… often supported by spending charts that also go up-and-to-the right. Creators / bettors / consumers are taking AI & Physical World Ramps = Fast + Data-Driven • Global Internet User Ramps Powered by AI from Get-Go = Growth We Have Not Seen Likes of Before • AI & Work Evolution = Real + Rapid 3 1 2 3 4 5 Operating Zone Market Share Source: YipitData (4/25) Global Internet User Ramps Powered by AI from Get-Go = Growth We Have Not Seen Likes of Before 7 Leading USA-Based LLM App Users by Region Note: Region