News for hackers. Stuff that matters.

A comment on Java JIT vs. Java AOT vs. Go for Small, Short-Lived Processes. Parent comment

Re:Java JIT vs. Java AOT vs. Go for Small, Short-Lived Proce... by kasperni on Tuesday December 24, 2019 @07:19PM (#21875851)
The overhead of, for example, invoking a method via reflection is measured in single-digit nanoseconds. Still not as fast as direct invocation, but unlikely to be a bottleneck unless you perform 10-of-millions of them per second.
[ Parent | on HN ]
Re:Java JIT vs. Java AOT vs. Go for Small, Short-Lived Proce... by LgWoodenBadger on Tuesday December 24, 2019 @08:00PM (#21876010)
Actually finding the method via reflection is the time consumer.

Once you have the method reference, actually invoking it isn’t any different than a regular method.

[ Parent | on HN ]
Re:Java JIT vs. Java AOT vs. Go for Small, Short-Lived Proce... by sk5t on Tuesday December 24, 2019 @11:54PM (#21876898)
Although I can't tell you why, it's been my experience that firing a simple method via reflection in both .NET and the JVM is roughly 2x the time of direct calls (or of calls via the 'dynamic' keyword in C#).
[ Parent | on HN ]