Advent of Code 2023 Solutions in Golang
Each day is it's own folder under cmd so they're all indivdually buildable. Solution is spoilered to avoid ruining it while wanting to look at just the performance results.
Problem Text: Link
Part 1: Link
Performance (AVG. Per Line):
Name CPU ns/op # bytes alloc'd per op # of allocs per op
BenchmarkProcessLine-8 14.27 ns/op 0 B/op 0 allocs/op
Part 2: Link
Performance (AVG. Per Line):
Name CPU ns/op # bytes alloc'd per op # of allocs per op
BenchmarkProcessLine-8 122.6 ns/op 0 B/op 0 allocs/op
Problem Text: Link
Part 1: Link
Performance (AVG. Per Line):
Name CPU ns/op # bytes alloc'd per op # of allocs per op
BenchmarkProcessGame-8 60.53 ns/op 0 B/op 0 allocs/op
Part 2: Link
Performance (AVG. Per Line):
Name CPU ns/op # bytes alloc'd per op # of allocs per op
BenchmarkProcessGame-8 138.33 ns/op 0 B/op 0 allocs/op
Problem Text: Link
Part 1: Link
Performance:
Name CPU ns/op # bytes alloc'd per op # of allocs per op
BenchmarkProcessEngine-8 103517 ns/op 0 B/op 0 allocs/op
Part 2: Link
Performance:
Name CPU ns/op # bytes alloc'd per op # of allocs per op
BenchmarkProcessEngine-8 68783 ns/op 0 B/op 0 allocs/opp
Problem Text: Link
Part 1: Link
Performance (AVG. Per Line):
Run Time [ using now:=time.Now() //do_work print(time.Since(now) ]: 25µs
Name CPU ns/op # bytes alloc'd per op # of allocs per op
BenchmarkProcessCards-8 2295 ns/op 0 B/op 0 allocs/op
Part 2: Link
Performance (AVG. Per Line):
Run Time [ using now:=time.Now() //do_work print(time.Since(now) ]: 20µs
Benchmark:
Name CPU ns/op # bytes alloc'd per op # of allocs per op
BenchmarkProcessCards-8 1263 ns/op 0 B/op 0 allocs/op