search

hstaudacher / osgi-jax-rs-connector

An OSGi - JAX-RS 2.0 Connector, software repository available on the link below
http://hstaudacher.github.io/osgi-jax-rs-connector
Other
190 stars 98 forks source link

Test 4.2.0 RC3 #81

Closed hstaudacher closed 9 years ago

hstaudacher commented 9 years ago

The RC3 is ready to be tested. There was a critical bug in RC2.

Maven: https://oss.sonatype.org/content/repositories/snapshots/ ziped p2 repo: https://dl.dropboxusercontent.com/u/5808972/com.eclipsesource.jaxrs.repository-4.2.0-RC3.zip

@kaikreuzer can you test it again with openHAB? @stefanseifert can you test the maven stuff? :)

BryanHunt commented 9 years ago

Is there a bndtools repo? I can test as well.

hstaudacher commented 9 years ago

Hi Bryan, I just ziped the prepared p2 repo. I have created the index.xml.gz as you have described it in #11

It currently upload to my dropbox. Will paste a link as soon as it is uploaded

hstaudacher commented 9 years ago

Here it is: https://dl.dropboxusercontent.com/u/5808972/osgi-jax-rs-connector-repo-4.2.0-RC3.zip

BryanHunt commented 9 years ago

Thanks. I'll give it a go.

kaikreuzer commented 9 years ago

I tested it with openHAB on a RasPi1 and it works as expected. The previous problems seem to be solved. I somehow do not get any logging from Jersey anymore in openHAB, so I cannot give detailed performance comparison data. It is not as fast as I would hope, but much faster than 4.1 at least. So I would approve the 4.2 release, although it might be worthwhile to further look into performance optimizations in the future.

hstaudacher commented 9 years ago

Alright. So, it's done. Will release 4.2 now.

hstaudacher commented 9 years ago

Thank you all for participating in this release. I think it's a good step forward.

@kaikreuzer do you have any ideas how to improve the performance further?

BryanHunt commented 9 years ago

@hstaudacher the index.xml is bad

kaikreuzer commented 9 years ago

@kaikreuzer do you have any ideas how to improve the performance further?

I wonder whether the "depend on all services" dependency might be a bottleneck. Maybe one could introduce an option to alternatively look for a specific service property. But I cannot tell if this would make a huge difference or not. Another thing that can help for the startup is the reduction of the size - 5.6MB is still pretty huge and I guess many parts of Jersey could be stripped out (e.g. the client).

hstaudacher commented 9 years ago

I think the only way we can improve this is to provide an automated performance test. Everything els eis speculation. I will open a separate issue for this ;)