Feb 14, 2025

It's entirely due to increase is-spent costs as shown in the performance trends above, due to rising conflicts and the associated paging costs. There are three ways to reduce the conflicts. (1) split the point hashes into another table, 1:1 with both arrays, so does not require another index or any more storage, (2) increase the spend hashmap bucket count to reduce hashmap conflicts, (3) increase the spend table hash key size to reduce secondary conflicts and therefore reads into the point hash table. I believe that (1) would bring it back to where it was before, or better, at least on the maxi. The others are space tradeoffs that will probably also help on the max but maybe not on the mini. None of the above changes would I expect to get the mini confirmation cost down significantly.