eclipse-ee4j / eclipse-ee4j/jersey
Jersey Performance Improvements
- Dominant language
- Java
- Stars
- 730
- Forks
- 382
- PR merge metrics
- No merged PRs in 30d
Description
According to a [scientific study of Catholic University of Colombia](https://www.researchgate.net/publication/325176403_JAX-RS_Implementations_A_Performance_Comparison), Jersey is **nearly just half** as fast as CXF (they compared Apache CXF 3.1.2 vs. Jersey 2.21, so I hope today it is not that bad anymore).
As a contributor and heavy user of Jersey I would really love to see (and possibly help with) improval of this situation.
Are there "official" plans to address performance in future or shall I just pick a profiler and start investigating? Or does anybody know a key issue already that I simply should start with?
Contributor guide
Research direction
The issue names no files, tests, or entry points. Start by reviewing the linked performance study and profiling current Jersey against CXF; define a specific hotspot and measurable target before changing code. Done would require an agreed performance improvement, but no scope or acceptance criteria are provided.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100