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

Adding automated localhost benchmark for OSX #1

Merged
merged 3 commits into from Jan 19, 2018

Conversation

jabrena
Copy link
Contributor

@jabrena jabrena commented Jan 14, 2018

Hi @spencergibb,

Using your notes from README, I have created a Script to test in OSX the whole process.
I can confirm your notes in a relative way.

The new Spring Gateway has improved the performance but it is true that Linkerd has a very good performance too but in all tests, the new gateway has the best results.

It could be interesting to deploy in CF the different ways to have a clean benchmark but in local, the results could orient the community.

It could be interesting to compare features between the new Spring Gateway and Linkerd in an Article.

Juan Antonio

wrk -t 10 -c 200 -d 30s http://localhost:8000/hello.txt
The whole process takes:

real    16m44.107s
user    6m18.181s
sys     6m28.601s

The host used for the benchmark is:
OSX 10.13.2
2.5 GHz Intel Core i5
16 GB 1867 MHz DDR3
benchmark.sh Outdated

OSX="OSX"
WIN="WIN"
LINUX="WIN"
Copy link

@Fydon Fydon Jan 17, 2018

Choose a reason for hiding this comment

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

Should this be LINUX="LINUX"?

@jabrena
Copy link
Contributor Author

jabrena commented Jan 17, 2018

Hi @Fydon,

You have reason.
I will upgrade the Script today.

@spencergibb
Copy link
Owner

I also run linux, so I couldn't test this.

@jabrena
Copy link
Contributor Author

jabrena commented Jan 19, 2018

Fixed minor change

@spencergibb
Copy link
Owner

@jabrena thanks for the contribution!

@jabrena
Copy link
Contributor Author

jabrena commented Jan 19, 2018

This weekend, I will try to move to Jmeter.

I tried to improve the wrk solution but the technical support is not fast.
wg/wrk#315

So, I will create a feature branch in my local repo to start with this process.
The idea is to reduce the benchmark execution time with a dynamic way to determinate the best jvm warnup for any gateway.

Later with a stable automated benchmark process, I will try to create a stage on Spring Cloud Gateway repo to automate the process to guarantee that the new Spring Gateway offers better performance than Netflix Zuul.

Juan Antonio

@spencergibb
Copy link
Owner

Sounds good

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

Successfully merging this pull request may close these issues.

None yet

3 participants