networknt / networknt/microservices-framework-benchmark
Fine tuning of JEE servers
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 715
- Forks
- 120
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
I would like to point out, that some parts of the benchmark are not really accurate, since they use default app server configs.
So Wildfly & Payara are using by default only 5 threads to serve any servlet (in the example JAX-RS).
Increasing the thread number & ejb pool may greatly increase these app server's throughput.
(I think the same would apply to Spring boot benchmarks).
Conclusion: please make a benchmark with fine tuned app servers to show the real capabilities of the given tech stack.
Also: in the light-java to my understanding, it is using servlet technology as-is, while JAX-RS adds a much heavier layer on the servlets (like parsing the incoming requests to DTOs and vice-versa or handling http requests based on the headers).
Conclusion: it would be good to see a simple code on top of a JEE or Servlet container, that only uses core JEE servlets to be measurable.
Thanks
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by locating the benchmark definitions for WildFly, Payara, Spring Boot, and the light-java case, then compare their server settings and request layers. Done means adding tuned server configurations and a core-servlet benchmark with results that can be compared consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring-boot
- Domain
- backend, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100