Thursday Feb 12, 2015

Jersey 2 Performance

During my sabbatical week in January i have done some performance improvements in Jersey server core module. These changes are already included in Jersey version 2.16.

To make sure the changes indeed made a positive difference i have re-established continuous performance testing for Jersey server side processing. These automated tests allowed Michal Gajdoš to collect some numbers that show how performance evolved within Jersey 2.x version space. In this post i would like to share part of the outcome of this measurement. I hope to be able to reveal more numbers and details on the test setup in later posts.

The above graph shows how Jersey throughput increased with increased Jersey version. Version 2.4 is emphasised here as till that version we had a serious bottleneck in Jersey, that avoided throughput to scale with increased number of worker threads.

The above numbers capture increased throughput for regular resource methods handling plain text payload, where no sub-resource locators are involved. Sub-resource locators used to have poor throughput in Jersey versions prior to 2.16. In 2.16 Michal fixed this and i would recommend you check out his post on this topic here.

I think that the above graph clearly shows that we take performance seriously in Jersey. I hope that we will be able to further improve performance of Jersey in future versions.

Wednesday Feb 22, 2012

Jersey 1.12 is released

We have just released the 1.12 version of Jersey, the open source, production quality, reference implementation of JAX-RS. The JAX-RS 1.1 specification is available at the JCP web site and also available in non-normative HTML here.

For an overview of JAX-RS features read the Jersey user guide. To get started with Jersey read the getting started section of that guide. To understand more about what Jersey depends on read the dependencies section of that guide. See change log here.

This version includes mainly bug fixes. The biggest update is Jersey asynchronous client switched internally from using Netty to Grizzly 2 client implementation. Grizzly 2 dependency was upgraded to version 2.2.1.

For feedback send email to:

users@jersey.java.net (archived here)

or log bugs/features here.

Besides 1.12, we have been working hard on our first public milestone for Jersey 2.0 and I am happy to let you know we have released that as well - see Marek's blog post for more details. As a result, Jersey 1.x releases may become less regular and we don't expect to add any bigger features going forward, as Jersey 2.0 becomes our main focus. We are planning to add some new exciting stuff there in the following months, so stay tuned!

Friday Nov 04, 2011

Jersey 1.10 is released

Yesterday, we have released the 1.10 version of Jersey, the open source, production quality, reference implementation of JAX-RS. The JAX-RS 1.1 specification is available at the JCP web site and also available in non-normative HTML here.

For an overview of JAX-RS features read the Jersey user guide. To get started with Jersey read the getting started section of that guide. To understand more about what Jersey depends on read the dependencies section of that guide. See change log here.

The major breaking change is we separated Servlet, EJB, and CDI functionality out from the jersey-server module and put this Java EE related stuff to a new, jersey-servlet module. Then when deploying into a Servlet container, you will need to add one more dependency (on that jersey-servlet module).

A similar change happened also to our jersey-grizzly2 module, where if you need the Grizzly Servlet server, you will newly need an additional, jersey-grizzly2-servlet dependency.

Another breaking change happened in the WADL area, where Pavel and Marek worked on improving and fixing bugs.

Last but not least, Pedro Kowalski from the user community contributed stream support to the jersey-multipart module.

For feedback send email to:

users@jersey.java.net (archived here)

or log bugs/features here.

Monday Sep 05, 2011

Jersey 1.9 is released

On the last Friday, we have released the 1.9 version of Jersey, the open source, production quality, reference implementation of JAX-RS. The JAX-RS 1.1 specification is available at the JCP web site and also available in non-normative HTML here.

For an overview of JAX-RS features read the Jersey user guide. To get started with Jersey read the getting started section of that guide. To understand more about what Jersey depends on read the dependencies section of that guide. See change log here.

Jersey artifacts are finally available in the central maven repositories. I.e. when using maven, you should not need to specify the <repositories/> tag any more. Snapshot versions of Jersey will become available in a new Java.net maven repository.

Besides a number of bug fixes, the major additions included in this version are: non-blocking asynchronous client feature (moved over to the contribs space from the experimental area, see Pavel's blog for details), FreeMarker support and WADL improvements made by Gerard Davison (see his blog post here), which allows you to automatically attach XML schema to the generated WADL.

For feedback send email to:

users@jersey.java.net (archived here)

or log bugs/features here.

Tuesday Jun 28, 2011

Jersey 1.8 is released

On the last Friday, we have released the 1.8 version of Jersey, the open source, production quality, reference implementation of JAX-RS. The JAX-RS 1.1 specification is available at the JCP web site and also available in non-normative HTML here.

For an overview of JAX-RS features read the Jersey user guide. To get started with Jersey read the getting started section of that guide. To understand more about what Jersey depends on read the dependencies section of that guide. See change log here.

This, 1.8, version of Jersey is going to be integrated into GlassFish 3.1.1 and contains bug fixes mainly. The most important fix from this perspective is included in the JAX-RS/EJB integration layer. It is now possible to implement JAX-RS resources as EJB Session beans, which implement local and/or remote interfaces. This functionality was broken in previous releases.

Another great addition should come into the client space, where Pavel has already done some preparation in the client API (including some breaking changes there) for the non-blocking asynchronous client feature. The implementation is already part of the experimental Jersey space and should be included as part of the stable Jersey bits in some of the coming releases.

For feedback send email to:

users@jersey.java.net (archived here)

or log bugs/features here.

Thursday Apr 14, 2011

JAX-RS Presentation at JavaOne in Moscow

I have just finished my JAX-RS presentation at JavaOne in Moscow. In fact, I have pretty much re-used what Paul and Roberto were presenting in San Francisco. Only dropped the EJB/CDI integration part to fit into the 45 minute time slot.

slides

demos

About

Jakub Podlesak

Search

Archives
« March 2015
SunMonTueWedThuFriSat
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
    
       
Today