It has been running in a intercontinental production environment with 100% read uptime since 2017.
It's 2000 lines of code: http://root.rupy.se (this test env. has 3 nodes: fem, six and sju)
It has been running in a intercontinental production environment with 100% read uptime since 2017.
It's 2000 lines of code: http://root.rupy.se (this test env. has 3 nodes: fem, six and sju)
Average is 4.8 millisec and 0.5 millisec respectively.
But those are just the JVM doing it's thing.
The numbers I like are these: 190.2 158 331
200ms global save average, 158ms min and 331ms max from europe to east+west US and Asia. Without fault, so consistent, much of that can be attributed to AWS improving so much over the years.
As to why the load/save are slower it's because the complete global roundtrip stats I only have for registers which are rare now so they don't hit the GC I'm guessing.
The thing I'm most proud of is async-to-async meaning the system will saturate all cores (without io-wait) on all machines without problems... it just keeps solving the problem at 100% efficiency, no memory leaks and 5 years uptime without any crashes.
Slowing down is the worst case, and if that is a problem just upgrade instance type, no uptime then though.