-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
utxo_total_supply
extremely slow
#158
Comments
What is |
Sorry, was working on adding that. See OP, here’s
|
Ah, so I guess this is expected, because it is loading all fuzz inputs. (The same would happen on merge or on This should be fixed the next time you pull from current Bitcoin Core Leave a comment here, if not. |
I see, I’ll update to the latest |
That’s better, but still a bit slow. Given that the fuzz test changed, I would expect that the runtime should already be reduced but even so. :-/ |
I don't know how to reduce the runtime further. Maybe assumeutxo can be used? If not, the only alternative would be to remove the target. |
I got a new faster computer. I fuzzed Doing a single run of all seeds on the
Doing a single run on my new corpus took only 101 seconds:
I do notice that my new corpus only achieved a |
iirc |
I was not, but either way, one being twice as fast as the other wouldn’t change much, should it? |
While I had noticed
utxo_total_supply
being extremely slow on a merge before, my nightly fuzzer has been on theutxo_total_supply
target for 6h51m at this point, even though the limit on the fuzzer is 3600 seconds. It seems to me that either it is stuck in an endless loop, or just extremely slow.My
[…]/qa-assets-active-fuzzing/fuzz_seed_corpus/utxo_total_supply
directory has 3250 seeds.It looks to me like it hasn’t even loaded my corpus yet:
Here are two of the worst offenders:
slow-unit-ec3af16aeb3b967f9b63edc7266a71f52825c616
/slow-unit-9c08c09c1d630fade4f699fdd1eeaa53325dcce3
The text was updated successfully, but these errors were encountered: