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

Write a Performance-Testsuite #217

Open
normanmaurer opened this issue Mar 5, 2012 · 11 comments
Open

Write a Performance-Testsuite #217

normanmaurer opened this issue Mar 5, 2012 · 11 comments
Assignees
Labels

Comments

@normanmaurer
Copy link
Member

As netty is really concerned about performance it would be really helpful to have some Testsuite that help us to see if a change does effect the throughput of netty.

At best the Testsuite would allow us to "plugin" different stuff to test different encoder/decoders and transport implementations.

I think the first goal would be to just test simple tcp echo stuff.

@jestan
Copy link
Member

jestan commented Mar 5, 2012

I have started something similar :), got the echo latency tests working https://github.com/jestan/netty-perf

@normanmaurer
Copy link
Member Author

Nice... Let me try to find time for review during the week

@normanmaurer
Copy link
Member Author

@jestan could you maybe write some docs which explains how-to use it ? So we could do perf testing before release ?

@jestan
Copy link
Member

jestan commented Oct 15, 2012

@normanmaurer Sure I will do.

@ghost ghost assigned trustin Jan 9, 2013
@trustin
Copy link
Member

trustin commented Jan 9, 2013

#899 will probably fix this issue.

@daschl
Copy link
Member

daschl commented Jan 13, 2014

#2085 may incorporate this?

@Scottmitch
Copy link
Member

@jestan @normanmaurer @daschl - Is this issue resolved with the introduction of the microbenchmark code?

@daschl
Copy link
Member

daschl commented Oct 5, 2014

I think so yes. Now its just a matter of adding things?

@normanmaurer
Copy link
Member Author

No I think it is still valid as we need to automate more complex tests

Am 23.09.2014 um 22:25 schrieb Scott Mitchell notifications@github.com:

@jestan @normanmaurer @daschl - Is this issue resolved with the introduction of the microbenchmark code?


Reply to this email directly or view it on GitHub.

@Scottmitch
Copy link
Member

@normanmaurer - Is it safe to move this to 5.0.0.Alpha3?

@normanmaurer
Copy link
Member Author

Yes

Am 06.10.2014 um 16:04 schrieb Scott Mitchell notifications@github.com:

@normanmaurer - Is it safe to move this to 5.0.0.Alpha3?


Reply to this email directly or view it on GitHub.

@Scottmitch Scottmitch modified the milestones: 5.0.0.Alpha3, 5.0.0.Alpha2 Oct 6, 2014
@trustin trustin modified the milestone: 5.0.0.Alpha3 Mar 7, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants