Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[#4284] Forward decoded messages more frequently #4322

Closed
wants to merge 1 commit into from

Conversation

normanmaurer
Copy link
Member

Motivation:

At the moment we only forward decoded messages that were added the out List once the full decode loop was completed. This has the affect that resources may not be released as fast as possible and as an application may incounter higher latency if the user triggeres a writeAndFlush(...) as a result of the decoded messages.

Modifications:

  • forward decoded messages after each decode call

Result:

Forwarding decoded messages through the pipeline in a more eager fashion.

@normanmaurer normanmaurer self-assigned this Oct 6, 2015
@normanmaurer normanmaurer added this to the 4.0.33.Final milestone Oct 6, 2015
@normanmaurer
Copy link
Member Author

@Scottmitch PTAL.

@ninja- this should help you...

@ninja-
Copy link

ninja- commented Oct 6, 2015

@normanmaurer looks good to me

@ninja-
Copy link

ninja- commented Oct 6, 2015

very creative way to keep the full API :P

for (int i = 0; i < size; i++) {
ctx.fireChannelRead(out.get(i));
}
fireChannelRead(ctx, out, size);
Copy link
Member

Choose a reason for hiding this comment

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

move into conditional below?

Copy link
Member Author

Choose a reason for hiding this comment

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

yep

@Scottmitch
Copy link
Member

@normanmaurer - Few questions. Lookin good.

@normanmaurer
Copy link
Member Author

@Scottmitch comments addressed

Motivation:

At the moment we only forward decoded messages that were added the out List once the full decode loop was completed. This has the affect that resources may not be released as fast as possible and as an application may incounter higher latency if the user triggeres a writeAndFlush(...) as a result of the decoded messages.

Modifications:

- forward decoded messages after each decode call

Result:

Forwarding decoded messages through the pipeline in a more eager fashion.
@normanmaurer
Copy link
Member Author

Cherry-picked into 4.0 (99dfc9e), 4.1 (11e8163 and master (a605fa4)

@normanmaurer normanmaurer deleted the fire_on_each_decode branch October 7, 2015 12:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants