Hi, I believe this is Kotlin related as I have an ...

# coroutines

[kubele]

Hi, I believe this is Kotlin related as I have an issue with coroutines.
Recently I've joined a project where Project Reactor is used with some light use of Coroutines and both approaches use scheduler with this config:

Schedulers.fromExecutor(Executors.newFixedThreadPool(75))

My problem is that when I rewrote this:

@GetMapping("/get-stuff")
fun getStuff(
    @RequestParam param: String
): Mono<ResponseObject> = Mono.fromCallable {
    service.getStuff(param = param)
}.subscribeOn(blockingScheduler)

to use coroutines:

@GetMapping("/get-stuff")
suspend fun getStuff(
    @RequestParam param: String
): ResponseObject = withContext(blockingScheduler.asCoroutineDispatcher()) {
    service.getStuff(param = param)
}

the memory usage has increased almost 2-3 times.
Do you have any idea why the performance might so much worse? That's something I definitely did not expect.
Edit: I forgot to mention - the behaviour was the same when we tried to use <http://Dispatchers.IO|Dispatchers.IO> instead of the scheduler
Slack Conversation

[xoangon]

Is the serviche exactly the same after the change to coroutines? I would guess it may be caused by it caching some responses.

For what I know, there shouldn't be any memory-related issues when migrating to coroutines

[kubele]

the only change in the service is the getStuff() is now suspend, otherwise it stays the same.

Yea, I didn't expect it either 😞