|<< Back to previous view|
[GLASSFISH-14957] [PERF] Optimize RESTful API such that in-process calls avoids the network overhead Created: 02/Dec/10 Updated: 15/Feb/13
|Fix Version/s:||future release|
|Reporter:||Jason Lee||Assignee:||Jason Lee|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
|Participants:||Jason Lee, ludo, Nazrul and Tom Mueller|
Paul Sandoz had mentioned the possibility of making Jersey avoid the network penalty when the client and server are in the same JVM. We need to investigate this to see if it's possible, as that could be a significant performance boost for the console.
|Comment by ludo [ 14/Dec/10 02:30 PM ]|
Note that it serializes and buffers the request and response entity if present. It might be possible to avoid that for the response entity, not sure about the request entity. It may also be possible under certain circumstances to match the request/response entity Java instances with the client and server and pass by reference but care has to be taken depending on what assumptions the app is running with.
IIRC you are depending on the injection of some Grizzly request/response artifacts. Under such circumstances those artifacts will not be injected, so you may need to abstract out that information."
Not sure about the lack of injection in some area...Might be more complicated than expected.
|Comment by Nazrul [ 20/Dec/10 05:31 PM ]|
Ludo mentioned that it is too risky to fix at this point. Excluding from 3.1 count.
|Comment by Tom Mueller [ 07/Feb/13 04:03 PM ]|
Reassigning to Jason as Ludo is no longer on the project.