4 ms·
"To reduce the GC impact from the storage engine, we considered different approaches and ultimately decided to develop a C++ storage engine to replace existing
by haglin 9y ago
"To reduce the GC impact from the storage engine, we considered different approaches and ultimately decided to develop a C++ storage engine to replace existing ones."
I wonder how the numbers would have looked with the new low latency GC for Hotspot (ZGC).
https://wiki.openjdk.java.net/display/zgc/Main https://wiki.openjdk.java.net/display/zgc/Main
Early results from SPECjbb2015 are impressive.
https://youtu.be/tShc0dyFtgw?t=5m1s https://youtu.be/tShc0dyFtgw?t=5m1s
- itronitron 9y agoyes, a comparison across multiple JVMs would be nice
- tibbetts 9y agoYes, also Azul Zing. Really anytime someone says they have a problem with GC and suggests spending a million dollars of engineer time building a new system, they should consider Zing first. It works and is a way more efficient way of spending money to fix GC latency problems.
- ADefenestrator 9y agoFor a small to medium sized shop, sure. For someplace with thousands or tens of thousands of nodes, the new system ends up cheaper in the long run.
- majidazimi 9y agoBecause GC related issues don't undergo from "problem" state to "solved" state. It is just a never ending stream of issues, that the team need to resolve, specially in a database realm in which metrics are hugely workload dependent.