Skip to content

Conversation

@timyates
Copy link
Contributor

We have many places where we are wrapping the responses in a Mono in the controllers.

As we declare @ExecuteOn(TaskExecutors.BLOCKING) in these controllers, I don't think this is required.

And it probably affects performance, as the work is probably offloaded multiple times to multiple thread pools.

This commit removes (almost) all of the wrapping. The only place it remains is in the Github client (as I'm not currently sure where that's used) 🤔

We have many places where we are wrapping the responses in a Mono in the controllers.

As we declare `@ExecuteOn(TaskExecutors.BLOCKING)` in these controllers, I don't think this is required.

And it probably affects performance, as the work is probably offloaded multiple times to multiple thread pools.

This commit removes (almost) all of the wrapping. The only place it remains is in the Github client (as I'm not currently sure where that's used) 🤔
@timyates timyates requested review from mkimberlin and sdelamo June 13, 2024 12:11
@timyates timyates self-assigned this Jun 13, 2024
@mkimberlin mkimberlin requested a review from weiqigao June 14, 2024 18:10
@timyates timyates requested a review from vhscom June 17, 2024 15:39
Copy link
Contributor

@vhscom vhscom left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great. This is going to make the codebase much easier to work with.

@mkimberlin mkimberlin merged commit 3682890 into develop Jun 17, 2024
@mkimberlin mkimberlin deleted the bugfix-remove-mono-wrapping branch June 17, 2024 18:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants