The code in the module has plenty of ObjectMapper instance creations, including one per feature read.That's inefficient, one should be created and shared, it's thread-safe but costly to create.See also:https://stackoverflow.com/questions/3907929/should-i-declare-jacksons-objectmapper-as-a-static-field
(Don't have a mandate to work on this right now, but should be a neat performance improv for the store)
fixed by during https://osgeo-org.atlassian.net/browse/GEOT-7055
Cool, I was worried about efficiency (but I was wanting it to work properly first)
pinging you for awareness
The code in the module has plenty of ObjectMapper instance creations, including one per feature read.
That's inefficient, one should be created and shared, it's thread-safe but costly to create.
See also:
https://stackoverflow.com/questions/3907929/should-i-declare-jacksons-objectmapper-as-a-static-field
(Don't have a mandate to work on this right now, but should be a neat performance improv for the store)