Consider optimising AbstractInvocationHandler::invoke

[rbalamohan]

On large deployments, due to very high number of executions, AbstractInvocationHandler::invoke shows up a hotspot. Snapshot of the profiler output is given below. Issue is due to the number of times, the if condition is evaluated, causing misses.

[simeonmalchev]

Hi Rajesh, thanks for submitting this PR. Did you actually manage to run some perf / benchmark tests that showed improvement when the calls to getXYZ methods are shortcut?

[simeonmalchev]

Thanks @rbalamohan, I just merged the PR. How urgent is to you to get out a build with this PR, I was planning to implement some other changes and push out a build after 2-3 weeks, is this late for you?

[rbalamohan]

Thanks a lot @simeonmalchev.
If we support minor incremental release, it would be great to have a release before that. We can deploy on production asap. :)

Otherwise, we can wait for the regular release cycle.

[rbalamohan]

Hi @simeonmalchev , Is there any possibility of having an early minor release?

[simeonmalchev]

@rbalamohan, yes, I'll push it over the weekend. I'll let you know once it is done..

[rbalamohan]

Thanks a lot @simeonmalchev

[simeonmalchev]

Fixed / PR merged in release 22.2.