Compiling Ruby to machine language

(patshaughnessy.net)

287 points todsacerdoti | 2 comments | 17 Nov 25 20:04 UTC | HN request time: 0.434s | source

Show context

cutler ◴[18 Nov 25 01:02 UTC] No.45960253[source]▶

Making dynamically typed, single threaded languages faster via JIT usually comes at the cost of a significant increase in memory consumption which for businesses smaller than Shopify is a much more significant factor.

replies(1): >>45962910 #

1. byroot ◴[18 Nov 25 08:58 UTC] No.45962910[source]▶

>>45960253 #

Is it? Smaller business usually comes with smaller applications. Most cloud and hardware vendors give you about 4GiB of RAM per core, maybe only 2 when using "CPU optimized instances", that's huge and leave plenty of space for a couple hundred MB of JITed code.

replies(1): >>45972939 #

2. MaxBarraclough ◴[18 Nov 25 22:12 UTC] No.45972939[source]▶

>>45962910 (TP) #

Agreed. In Java land, if I understand correctly the OpenJ9 JVM can (or at least could) beat HotSpot in memory consumption, while being slightly behind in execution times. It still sees only limited adoption. This may be just because it's seen as an 'alternative' option, less trustworthy than HotSpot, but it also seems to indicate the HotSpot developers aren't prioritising memory consumption.

https://bell-sw.com/announcements/2022/06/28/hotspot-vs-open...

https://eclipse.dev/openj9/performance/ (non-impartial source, of course)

↑