pad-motion VS stretto

Luckily after tons of searching I found a obscure bare-bones program with a whopping zero documentation called Pad Motion, which seems to be the ONLY mouse-to-motion solution for cemuhook. It works, but the sensitivity is way too high and the x axis is inverted. Unfortunately the program has absolutely no customizability, so you're stuck with what it gives you. Plus Yuzu has no ability to invert motion controls and MPR lacks the feature as well.

Hi, I think this link is a good explanation https://github.com/al8n/stretto/pull/7

Ya, I saw concache but I looked into it and it doesn't implement what is needed. Each bucket has its own linked-list backing (hence "lock-free linked list buckets"). An LRU needs each value in each bucket to be part of one linked list I believe. After posting this I realized my line of research was failing because it was state of the art five years ago. Caffeine replaced `concurrentlinkedhashmap` in the java world (by the same author). A rust version of that is Moka. These are much more complicated than a concurrent LRU but faster (aka more state of the art). Another rust crate is Stretto which is a port of dgraph's Ristretto (in go). The question becomes is it worth it to essentially port `concurrentlinkedhashmap` to have a great concurrent LRU when there are more state of the art caches out there.

For the case in the benches folder(a very roughly bench case), stretto is around 20 - 30 ms(sync version is around 30 - 40 ms) faster than moka, for 120, 000+ operations. I set stretto to collect metrics when benching, collecting metrics will make around 10% overhead. Moka seems not to provide a configuration to collect the metrics, so the hit-ratio is not compared.