When java.net is responsive (sigh...), I will file this issue:
When I make a single request to a servlet, the
com.sun.grizzly.rcp.Request and Response objects are recycled twice:
once from com.sun.grizzly.tcp.http11.InternalInputBuffer.nextRequest(),
and once from com.sun.grizzly.rcp.StaticResourcesAdapter.afterService().
I'm not yet sure of the impact of this. Profiles tell me that the time
spent recycling is 2x in v3 compared to v2, and that's about 2% of total
time (so a 1% regression from v2). Though I commented out one of the
recycle calls and didn't see an improvement -- so I likely have a
bottleneck somewhere else, or I didn't understand the code path enough.
It might be that other processing in nextRequest and afterService is
also duplicated?
-Scott