-
Story
-
Resolution: Done
-
Medium
-
None
-
None
-
None
Generated vpp-japi (part of VPP project) today is asynchronous and works, but there are some drawbacks:
Not really asynchronous from Java perspective, requires Java to perform active wait loops (for all generated functions) – big overhead due to JNI boundary being crossed lots of times Requires hand crafted implementations for dump calls The japi should be:
Truly asynchronous with callbacks into Java Lightweight (no caching in the C code, generate all the methods except connect, disconnect and ping etc.)
- blocks
-
HONEYCOMB-40 Honeycomb stops responding to requests
- Complete
- relates to
-
JVPP-16 Improve jvpp performance
- To Do
1.
|
Design new version of japi with above requirements | Complete | Marek Gradzki | |
2.
|
Document and put on wiki | Complete | Maroš Maršalek | |
3.
|
Implement a POC to verify and measure base performance | Complete | Maroš Maršalek | |
4.
|
Develop the POC into a full japi v2 | Complete | Marek Gradzki | |
5.
|
Migrate Honeycomb to use vpp-japi v2 | Complete | Marek Gradzki | |
6.
|
Deprecate vpp-japi | Complete | Marek Gradzki | |
7.
|
Remove vpp-japi | Complete | Marek Gradzki |