There is not really any low hanging fruit that I am aware of to make
that particular benchmark run faster.
One of the easiest ways to get it to run faster would be to strip out
all the Undertow code that is not relevant to the benchmark, however
that would not be particularly useful in the real world :-)
I do have a few ideas about what may help (the biggest one being lazy
allocation of headers to reduce allocations even further), however
this may not be possible without some API modifications, is a fair bit
of work, and may not actually help.
Feel free to profile it and if you can make some improvements that is
great, but I don't think there are any easy improvements any more.
Stuart
On Fri, Apr 8, 2016 at 4:52 AM, Miere Teixeira <miere.teixeira(a)gmail.com> wrote:
Hi Stuart,
I've followed undertow benchmark on Techempower's Benchmark page almost 2
years and I've noticed that undertow's benchmark code has not been updated
since last year.
I'd like to know what are your tips to improve Undertow's performance on TE
Benchmark.
Regards
_______________________________________________
undertow-dev mailing list
undertow-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/undertow-dev