|
|
|
|
|
|
by kstenerud
1878 days ago
|
|
|
Yup, and go is particularly bad for this because it handles allocations automatically (and poorly). I can double a go program's performance by going through the memory profile and rearranging the instructions to minimize hidden applications. The worst offender is slices, since you can't mark them read only or stack allocated. |
|
|