[resteasy-dev] Caching of ResteasyUriInfo in org.jboss.resteasy.plugins.server.servlet.ServletUtil

[Alessio Soldano]

Hi John,
interesting data, thanks. Yes, I think it would make sense to have some
cache; can you share a link to the hibernate caching mechanism that you're
referring to?
Thanks

On Sat, Oct 27, 2018 at 2:00 AM John O'Hara <johara at redhat.com> wrote:

> During a benchmark run, we are seeing over 5% of cpu time taken up by each
> request creating a new ResteasyUriInfo instance. Please see the attached
> graph.
>
> For most use cases in our application, the parameters are the same between
> requests, and therefore the ResteasyUriInfo are immutable and could be
> shared. The case that I can see where sharing a ResteasyUriInfo would be
> problematic is when there are path parameters in the URI.
>
> Could it be possible to cache ResteasyUriInfo that are immutable, or even
> cache a URI with placeholders for URI that contain path parameters?
>
> IIRC hibernate has a similar caching mechanism for prepared statements
> with parameters, a similar approach may work here.
>
> Thanks,
>
> John
>
> --
>
> JOHN O'HARA
>
> PRINCIPAL SOFTWARE ENGINEER
>
> Red Hat <https://www.redhat.com/>
> <https://red.ht/sig>
> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
> @redhat <https://twitter.com/redhat>   @redhatinc
> <https://instagram.com/redhatinc>   @redhatsnaps
> <https://snapchat.com/add/redhatsnaps>
> _______________________________________________
> resteasy-dev mailing list
> resteasy-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/resteasy-dev
>


-- 

Alessio Soldano

Associate Manager

Red Hat

<https://www.redhat.com>
<https://red.ht/sig>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/resteasy-dev/attachments/20181027/580f92e9/attachment.html