Prelude This is the third post in a three part series that will provide an understanding of the mechanics and semantics behind the garbage collector in Go. This post focuses on how the GC paces itself. Index of the three part series: 1) Garbage Collection In Go : Part I - Semantics 2) Garbage Collection In Go : Part II - GC Traces 2) Garbage Collection In Go : Part III - GC Pacing
Continue reading

“Once a language gets complex enough, programming in it is more like carving out a subset from an infinite sea of features, most of which we’ll never learn. Once a language feels infinite, the costs of adding further features to it are no longer apparent”. - Mark Miller The new try proposal is an addition to the language that introduces a second mechanic to handle errors. It is being introduced in response to data gathered from the 2018 Go Survey and a review of proposals that were submitted during the Go 2 proposal process.
Continue reading

Prelude This is the second post in a three part series that will provide an understanding of the mechanics and semantics behind the garbage collector in Go. This post focuses on how to generate GC traces and interpret them. Index of the three part series: 1) Garbage Collection In Go : Part I - Semantics 2) Garbage Collection In Go : Part II - GC Traces 2) Garbage Collection In Go : Part III - GC Pacing
Continue reading

Prelude This is the first post in a three part series that will provide an understanding of the mechanics and semantics behind the garbage collector in Go. This post focuses on the foundation material on the collector’s semantics. Index of the three part series: 1) Garbage Collection In Go : Part I - Semantics 2) Garbage Collection In Go : Part II - GC Traces 2) Garbage Collection In Go : Part III - GC Pacing
Continue reading

One of the traps of concurrency is “incomplete work” which occurs when a program terminates before outstanding Goroutines complete. Depending on the program, this may be a serious problem. This post demonstrates the trap and discusses possible solutions.
Continue reading

Integration tests give insights to the end-to-end operation of web services. In part 1 of this 3 part series over integration testing in Go we explore how to run integration tests in restrictive environments, such as Jenkins.
Continue reading

Goroutine Leaks are a common cause of memory leaks in Go programs. In my previous post, I presented an introduction to Goroutine leaks and provided one example of a common mistake that many Go developers make. Continuing that work, this post presents another scenario on how Goroutines could be leaked.
Continue reading

Prelude This is the third post in a three part series that will provide an understanding of the mechanics and semantics behind the scheduler in Go. This post focuses on concurrency. Index of the three part series: 1) Scheduling In Go : Part I - OS Scheduler 2) Scheduling In Go : Part II - Go Scheduler 3) Scheduling In Go : Part III - Concurrency Introduction When I’m solving a problem, especially if it’s a new problem, I don’t initially think about whether concurrency is a good fit or not.
Continue reading

Goroutine leaks are a common source of memory leaks in concurrent programs. This post defines Goroutine leaks and provides one example of a leak that is easy to miss in production code.
Continue reading

Prelude This is the second post in a three part series that will provide an understanding of the mechanics and semantics behind the scheduler in Go. This post focuses on the Go scheduler. Index of the three part series: 1) Scheduling In Go : Part I - OS Scheduler 2) Scheduling In Go : Part II - Go Scheduler 3) Scheduling In Go : Part III - Concurrency Introduction In the first part of this scheduling series, I explained aspects of the operating-system scheduler that I believe are important in understanding and appreciating the semantics of the Go scheduler.
Continue reading