Reduce reflection in LocationDetailQueryMapper
When profiling we encountered this (less severe) hotspot: Class.getDeclaredMethod()
is a very expensive call (~0.15% CPU load in connection phase). In LocationDetailQueryMapper
, the result of the call can easily be cached for future reference.
Edited by Winfried Gerlach