13:55:27 <m-relay> <t​obtoht:monero.social> Ah, my bad. I didn't think about how significant the performance penalty for a debug build would be.
13:55:34 <m-relay> <t​obtoht:monero.social> Here are my numbers for a release build with Rust 1.82:
13:55:39 <m-relay> <t​obtoht:monero.social> 1-in: 1.2s, 2-in: 1.5s, 4-in: 2.4s, 8-in: 4.4s
14:02:17 <m-relay> <j​effro256:monero.social> tobtoht: there's tons of debug assert statements in the rust crate that do a lot of crypto arithmetic which slows down debug builds
14:09:31 <m-relay> <t​obtoht:monero.social> Ok, makes perfect sense then.
15:19:39 <m-relay> <j​berman:monero.social> Bah, should have realized that's debug, lol
15:19:59 <m-relay> <j​berman:monero.social> (I should have*)
15:41:25 <m-relay> <j​berman:monero.social> anyways, ya with this blinds cache + with removing multiple rounds of blinds calculations, that should end up close to instant in the normal case
16:35:48 <m-relay> <j​berman:monero.social> actually it should always be close to instant the way it's being implemented, except for the case where the wallet identifies a ton of received outputs without doing the normal scan flow (e.g. using the scan_tx feature) and the wallet tries to spend those outputs