mknyszek

4 ms·

1.
by mknyszek 1mo ago
There's a little more nuance to this. The compiler knows the static type of any value placed into an interface value, and emits code to place a concrete type pointer (or itab pointer) into the interface value. You can see this in the d
2.
by mknyszek 7mo ago
I think this is a misunderstanding. If the program out-paces the GC because the GC guessed the trigger point wrong, something has to give. In Go, what gives is goroutines have to use some of their time slice to assist the GC and pay down th
3.
by mknyszek 7mo ago
> Thus, they’ll probably never fix it. I'm sorry you had a bad experience with Go. What makes you say this? Have you filed an issue upstream yet? If not, I encourage you to do so. I can't promise it'll be fixed or delved i
4.
by mknyszek 7mo ago
The compiler generates code to spill arguments to the stack at synchronous preemption points (function entry). Signal-based preemption has a spill path that saves the full ABI register set.
5.
by mknyszek 2y ago
Yep! I was on my phone, sorry about that. Did it ever used to only show wall time? Or am I just completely misremembering?
6.
by mknyszek 2y ago
Fascinating. I could see the Serial GC, if it's generational, just totally crush this particular benchmark. I wonder what the heap size heuristic is for the Serial GC. > Don't forget that the JVM has to allocate memory for all
7.
by mknyszek 2y ago
I just meant that you cannot easily see wall time and memory use together on the same page. (I would love to be wrong about that.)
8.
by mknyszek 2y ago
Looking at only the CPU numbers from this benchmark is misleading. This site requires the use of default configurations for each language runtime, and JVMs tend to have a much larger default heap than the Go runtime. Tracing GCs tend to hav
9.
by mknyszek 4y ago
> At no point is it invalidated, and the new arena will now start allocating new stuff from the start of the chunk. Right? And my old pointer still works, and the data inside it is at some point overwritten. It doesn't allocate at t
10.
by mknyszek 4y ago
The functionality to poison the address space is there, and it does work. What you're encountering is one of two exceptions in the implementation where you might not get an immediate failure: 1. If you use only a very small amount of
11.
by mknyszek 7y ago
> He is also the maintainer of JMH, Java Microbenchmarking Harness, a tool I miss in about every other language especially Go. Because writing microbenchmarks is really difficult especially on a JIT that wants to rewritw and optimize thi