Optimize Coroutine invocations

[sdeleuze]

KClass instantiation in CoroutinesUtils is suboptimal, and should be replaced by KTypes#isSubtypeOf checks using pre-instantiated types for Flow, Mono and Publisher.

[sdeleuze]

This commit impact on performances is significant since a throughput increase between 2x and 3x has been measured on basic endpoints.

[sdeleuze]

@koo-taejin @efemoney Please test the latest 6.1.5-SNAPSHOT builds and report if you see some unexpected side effects.

[efemoney]

Tested from my side & passes all my tests 👍🏾 just like the previous snapshot

[koo-taejin]

I am going to test it. 👍 thanks :)

[koo-taejin]

Unfortunately, I don't think the situation has changed much.
It would be accurate to put it into production and test it, but I apologize for not being able to do this.

Method of getClassifier() has been replaced by method of getJvmErasure().
I had checked that getClassifier() is called from getJvmErasure().
(in org.springframework.core.CoroutinesUtils.lambda$invokeSuspendingFunction$2(Object[], KFunction, Object, CoroutineScope, Continuation))

• spring-boot 3.2.0
  

• spring-boot 3.2.1 with 6.1.5-SNAPSHOT-p1
  

• spring-boot 3.2.1 with 6.1.5-SNAPSHOT-p2
  

Also, in the latest version, the isSubTypeOf() method uses resources.
(in org.springframework.core.CoroutinesUtils#invokeSuspendingFunction(kotlin.coroutines.CoroutineContext, java.lang.reflect.Method, java.lang.Object, java.lang.Object...))

• spring-boot 3.2.1 with 6.1.5-SNAPSHOT-p1
  

• spring-boot 3.2.1 with 6.1.5-SNAPSHOT-p2
  

This is called for every suspend function, so more use Coroutines, the bigger the impact seems to be.

If there is anything I can do to help, please let me know.

Thank you so much. 🙇

[sdeleuze]

See this related comment.