> I would have thought that you wouldn't wait for 10,000 iterations I haven't kept up with Ruby JITs, so I don't know if / how mjit handles inlining, but what

> I would have thought that you wouldn't wait for 10,000 iterations I haven't kept up with Ruby JITs, so I don't know if / how mjit handles inlining, but what I remember from my J9 / OMR days is that choosing what to inline made a massive difference in compiled code performance. Inlining too much was a great way to hobble performance. > Flush less frequently or no-longer needed compiled calls... The technical complexity of this process should not be underestimated. Given the minimalism of mjit's approach, I could easily see such a strategy being unviable without infrastructure investment that would (at least appear to) be significantly further along the effort / reward curve.