I was just profiling my latest Domino JNA feature "VirtualViews" to rebuild Domino views and the QueryResultsProcessor logic in Java code, when I came across this call tree:
In my test, I am processing 40.000 fakename docs into a categorized view, so small code changes add up.
But I think we should change the innards conversion in JNX as well and replace this line:
final LocalDate utcDate = LocalDate.now().with(JulianFields.JULIAN_DAY, julianDay);
with this:
final LocalDate utcDate = LocalDate.of(1970,1,1).with(JulianFields.JULIAN_DAY, julianDay);
or a similar solution. Looks like the LocalDate.now() function does some timezone stuff internally that is not cheap.
I was just profiling my latest Domino JNA feature "VirtualViews" to rebuild Domino views and the QueryResultsProcessor logic in Java code, when I came across this call tree:![image](https://github.com/HCL-TECH-SOFTWARE/domino-jnx/assets/4291861/bb1deb3b-14dd-4737-a058-b10f0cac8b4f)
In my test, I am processing 40.000 fakename docs into a categorized view, so small code changes add up. But I think we should change the innards conversion in JNX as well and replace this line:
with this:
or a similar solution. Looks like the LocalDate.now() function does some timezone stuff internally that is not cheap.
After my change, the call tree looked better.