5个可以在Golang中优化代码以提高性能的技巧分享

// Bad: Passing a large slice by pointer
func slowFunction(s *[]int) {
	// do something with s
}

// Good: Passing a large slice by value
func fastFunction(s []int) {
 // do something with s
}

// Bad: Allocating a new slice for each iteration
for i := 0; i < 100; i++ {
	s := make([]int, 10)
	// do something with s
}

// Good: Reusing the same slice
s := make([]int, 10)
for i := 0; i < 100; i++ {
 // do something with s
}

// Bad: Using a slice to store key-value pairs
type Pair struct {
	key   string
	value int
}
pairs := []Pair{}

// Good: Using a map to store key-value pairs
pairs := make(map[string]int)

// Bad: Spawning a new goroutine for each iteration
for i := 0; i < 100; i++ {
	go func() {
		// do something concurrently
	}()
}

// Good: Using a fixed number of goroutines
const numWorkers = 10
jobs := make(chan int, 100)
for i := 0; i < numWorkers; i++ {
 go func() {
  for j := range jobs {
   // do something concurrently
  }
 }()
}

// Using the pprof tool to profile CPU usage
go test -run=^$ -bench=. -cpuprofile=cpu.out
go tool pprof cpu.out

// Using the go test -bench flag to benchmark performance
func BenchmarkMyFunction(b *testing.B) {
 for i := 0; i < b.N; i++ {
  MyFunction()
 }
}
go test -bench=BenchmarkMyFunction