Skip to content
New issue

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

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

Already on GitHub? # to your account

Update all play2-java benchmark projects #3061

Merged
merged 1 commit into from
Nov 13, 2017

Conversation

mkurz
Copy link
Contributor

@mkurz mkurz commented Nov 12, 2017

This pull request upgrades all the play2-java projects to the latest Play version. Play now uses akka-http by default.

I have three questions:

  • Will there be another preview round?
  • The TechEmpower benchmark environment uses 2 x 4-Core E5520 CPUs in the database server - so that is 8 physical cores? Is that correct? (Needed for db pool and thread pool sizing)
  • How can I change the name of the benchmark project in the result table? It looks like e.g. "display_name": "play2-java-jpa-hikaricp" from the benchmark_config.json does not get picked up, instead I see this:
    name
    Why is the project named play-java-jpa? I can not figure out how that name is composed...

@NateBrady23
Copy link
Member

  • There will probably be a couple more preview rounds, since we had some longer than expected downtime
  • Yes, 16 Hyperthreaded cores / 8 physical cores
  • I believe we have a hard-coded map of frameworks on the results site to create smaller links for sharing filtered links. I'll see if we can get that updated for you

@NateBrady23 NateBrady23 merged commit 4401dfb into TechEmpower:master Nov 13, 2017
@mkurz mkurz deleted the upgradePlayJavaProjects branch November 13, 2017 01:52
@mkurz
Copy link
Contributor Author

mkurz commented Nov 13, 2017

@nbrady-techempower Thanks for your answers!

@wsargent
Copy link

wsargent commented Nov 14, 2017

@mkurz https://github.com/tenorviol/play-c100k-test may be useful as a reference as well -- I added a pull request for native option: tenorviol/play-c100k-test#1

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

Successfully merging this pull request may close these issues.

3 participants