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

[feature] Allow easy measurement of handlers in a pipeline #2810

Open
diwakergupta opened this issue Aug 22, 2014 · 1 comment
Open

[feature] Allow easy measurement of handlers in a pipeline #2810

diwakergupta opened this issue Aug 22, 2014 · 1 comment

Comments

@diwakergupta
Copy link

E.g. I want to spend how much time my application is spending in the SSLHandler. It is near impossible to do this today, apart from some clunky hacks that may end up polluting the measurements.

Copying relevant bits from IRC:

[11:40:57]  <diwaker>    trying to figure out the best way to measure the time spent in each of the handlers in my pipeline
[11:41:06]  <diwaker>    surely someone has written a handler decorator for this? :-)
[11:41:19]  <diwaker>    any suggestions on doing this the netty way are much appreciated!
[11:47:35]  <@normanm>   diwaker the problem is that each handler will call the next one
[11:48:39]  <diwaker>    right so a really crude way out be to insert dummy handlers before/after the handler I want
[11:48:47]  <diwaker>    and measure time in those
[11:49:15]  <diwaker>    I'm specifically interested in measuring the SSLHandler performance and don't see any existing hooks for that :/
[11:49:34]  <diwaker>    normanm: surely I'm not the only one who's wanted to do this? ;-)
[11:50:08]  <@normanm>   I think the right way would in DefaultChannelHandlerContext
[11:50:18]  <@normanm>   can you add a github issue ?
@WhiteTrashLord
Copy link

The performance of the Java based SSL Handler is bad. You should switch to native SSL solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants