Re:Zinc Search engine. A lightweight alternative to Elastics...
by kaba0 on Saturday December 04, 2021 @04:27PM
(#29444476)
It is not expected at all in like a decade (and even previously, it was mostly blog articles for very specific workloads, being out of date soon after publication).
The default G1 GC is perfectly fine for the vast majority of workloads as is. In the rare case it is needed, the target pause time setting can be used to swift our preference of latency vs throughput.
Elasticsearch restarting due to out of memory errors was a common occurrence at my last gig where we used it heavily.
The difference between Java GC and Go GC is stark. In several years, I've never had to touch a GC knob on Go, but in Java it is expected, and not usually worth the effort.