...
The cited article also shows benchmarks from 2017 in which Jackson parser was out performing GSON in the large file category. We can surmise that there is a constant battle between these objectMappers and Jackson may begin out performing GSON again in the future. For example this article from 2019 with new benchmarks states that the difference between the different mappers is negligible, with Jackson mapper having a slight lead with larger files.
Test Results
| Parser | Operation | Execution time in microseconds | Issues | |||
|---|---|---|---|---|---|---|
| 40 characters | 100 characters | 1000 characters | ||||
| Jackson | Read | 7.488 | 10.984 | 50.49 11 | 50 | |
| GSON | Read | 0.509 | 0.818 <1 | <1 | 8.212 | GSON parses all numerical values to Doubles and as such it unable to dynamically allocate the object type that it is parsing |
| Jackson | Write | 0.296 | 0.567 <1 | <1 | 5.12 | |
| GSON | Write | 0.531 <1 | 1.332 14.884 | 15 | ||
| Parser | Pros | Cons |
|---|---|---|
| Jackson | Consistent conversion of numerics | Slower Read |
| GSON | Faster Reads | Converts numerics to Doubles |
...
- CpsDataPersistenceServiceImpl.java is using two mapper objects, GSON and Jackson, should be just Jackson
- NetworkCmProxyInventoryController.java is using the Jackson mapper where the GSON could be used instead
- NetworkCmProxyDataServiceImpl.java is using the Jackson mapper where the GSON could be used instead
Temporal
...
- Jackson
...
Independent Testing Output
...