> By killing Memory Arenas, Go effectively capped its performance ceiling. I'm still optimistic about potential improvements. (Granted, I doubt there will be anything landing in the near future beyond what the author…
For in-process go scheduling, some progress has been made here; see: https://go.dev/blog/synctest But `synctest.Wait` won't work for non-durably blocked goroutines (such as in the middle of a TCP syscall) so requires…
(Admitting bias: I've only ever worked with postgres in production with update-heavy tables so I've dealt with more of its problems than MySQL's) Postgres also has other gotchas with indexes - MVCC row visibility isn't…
> By killing Memory Arenas, Go effectively capped its performance ceiling. I'm still optimistic about potential improvements. (Granted, I doubt there will be anything landing in the near future beyond what the author…
For in-process go scheduling, some progress has been made here; see: https://go.dev/blog/synctest But `synctest.Wait` won't work for non-durably blocked goroutines (such as in the middle of a TCP syscall) so requires…
(Admitting bias: I've only ever worked with postgres in production with update-heavy tables so I've dealt with more of its problems than MySQL's) Postgres also has other gotchas with indexes - MVCC row visibility isn't…