Hi Vishal,
We have not done any performance work on Jersey, currently it is likely
to be slow compared to more mature Web frameworks.
Since the project is still in its early stages i want to get things
functional correct and not prematurely optimize (especially when the API
is likely to change).
That is not to say i don't think performance is very important. It is
definitely something we will work on as the release matures towards 1.0.
For example, i would like to use byte code injection on resource classes
rather than using reflection as i suspect this will be one area that
will show up in hot spots after "low-hanging fruit" has been optimized.
However, this is tricky intricate work that requires a stable API plus
some existing implementation experience. Further more, when we measure
we may pleasantly find that such work is not required :-) but i suspect not.
Having said that there are some abnormally slow areas i need to fix
around caching of service providers... i don't want to give the bad
impression that performance completely sucks :-)
Paul.
Vishal Vatsa wrote:
> Hey Guys,
>
> Has any one done any kind of request bench mark on jersey,
> I was wondering how requests my should be able to handle ?
>
> Thanks
> Vishal
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jersey.dev.java.net
> For additional commands, e-mail: users-help_at_jersey.dev.java.net
>
--
| ? + ? = To question
----------------\
Paul Sandoz
x38109
+33-4-76188109