Håvard M. Ottestad

## Before ``` Benchmark Mode Cnt Score Error Units GetStatementsBenchmark.getTypesAndLabels avgt 5 138.205 ± 3.405 ms/op GetStatementsBenchmark.groupByLanguage avgt 5 0.395 ± 0.035 ms/op GetStatementsBenchmark.groupByType avgt 5 5.550 ± 1.104 ms/op...

At the moment I haven't found any existing benchmarks that are improved in this branch. The changes are based on my WIP performance branch #3854. Fixing one bottle neck will...

## Before ``` Benchmark (param) Mode Cnt Score Error Units ReasoningBenchmark.forwardChainingSchemaCachingRDFSInferencer moreRdfs::12180 avgt 5 11.254 ± 0.163 ms/op ReasoningBenchmark.forwardChainingSchemaCachingRDFSInferencer longChain::5803 avgt 5 8.083 ± 0.048 ms/op ReasoningBenchmark.forwardChainingSchemaCachingRDFSInferencer medium::544 avgt 5...

``` Left is after, right is before. Benchmark Mode Cnt Score Score Error Units IsomorphicBenchmark.blankNodes avgt 2 5.570 4.998 ms/op IsomorphicBenchmark.blankNodesLarge avgt 2 7001.437 6964.143 ms/op IsomorphicBenchmark.bsbm avgt 2 39.047...

At least on this very short benchmark run it didn't seem to make much difference.

Yeah, thought it was cool. I read about using XOR just the other day on hackernews so wanted to give it a shot. Gonna leave this up here though and...

I think we need some GC sensitive benchmarks for the isomorphic method.

Marked this as stale to signal that the PR hasn't been active for a while and that we should consider closing it.

Marked this as stale to signal that the PR hasn't been active for a while and that we should consider closing it.

Could an easy fix be to do an instanceof check and call `.atOffset(ZoneOffset.UTC)`? Or is it that the milliseconds resolution is higher for Instant than for the XML calendar spec?