5 ms·

Awesome work! In our shop, we managed to solve significant application bottlenecks simply by switching to Shenandoah GC. The application in question is very com

by dig1 5y ago

Awesome work! In our shop, we managed to solve significant application bottlenecks simply by switching to Shenandoah GC. The application in question is very complex, so any kind of rewrite in another language is out of the question. This is the power of JVM we do not get from other languages/VMs. Kudos to JVM (previous and current) architects, developers, and everyone involved with it.

dis-sys 5y ago
> This is the power of JVM we do not get from other languages/VMs. sub-millisecond gc pause has been available to Golang users for ages.
- awild 5y ago
  I'm guessing the parent is referring to the ability to transparently change runtime parameters and benefit from technical improvements without having to switch languages or even needing recompilation. That's not something golang can do given its statically linked afaik
  - dig1 5y ago
    Exactly!
- kaba0 5y ago
  Only by not allocating garbage in the first place by using “value types”. No way its GC would even get close to the JVM’s (and certain problems do require garbage collection, where the JVM will have better throughput)
bjarneh 5y ago
> The application in question is very complex, so any kind of rewrite in another language is out of the question. I think I know what you mean. If a couple of guys quit, the company is in major trouble? :-) Forgot this: /s
- brianmcc 5y ago
  Not the OP but you can have a large, complex system that's widely understood and supported by a decent sized team, where a rewrite is still not a commercially wise choice
  - dig1 5y ago
    True!
  - jacquesm 5y ago
    This is probably the norm.
  - FieryTransition 5y ago
    Yeah, rewriting everything is almost never a good choice from a business value perspective. Usually, the most sensible thing to do, is to break the system up in components, and rewrite them slowly while keeping interop with the old system. Downtime is no money time. And new features sometimes give more value, even if the programmer is grumpy.
- deleted 5y ago
  [deleted]

by dig1 5y ago

dis-sys 5y ago

> This is the power of JVM we do not get from other languages/VMs. sub-millisecond gc pause has been available to Golang users for ages.

awild 5y ago
I'm guessing the parent is referring to the ability to transparently change runtime parameters and benefit from technical improvements without having to switch languages or even needing recompilation. That's not something golang can do given its statically linked afaik
- dig1 5y ago
  Exactly!
kaba0 5y ago
Only by not allocating garbage in the first place by using “value types”. No way its GC would even get close to the JVM’s (and certain problems do require garbage collection, where the JVM will have better throughput)

bjarneh 5y ago

> The application in question is very complex, so any kind of rewrite in another language is out of the question. I think I know what you mean. If a couple of guys quit, the company is in major trouble? :-) Forgot this: /s

brianmcc 5y ago
Not the OP but you can have a large, complex system that's widely understood and supported by a decent sized team, where a rewrite is still not a commercially wise choice
- dig1 5y ago
  True!
- jacquesm 5y ago
  This is probably the norm.
- FieryTransition 5y ago
  Yeah, rewriting everything is almost never a good choice from a business value perspective. Usually, the most sensible thing to do, is to break the system up in components, and rewrite them slowly while keeping interop with the old system. Downtime is no money time. And new features sometimes give more value, even if the programmer is grumpy.
deleted 5y ago
[deleted]