mirror of
https://github.com/ElementsProject/lightning.git
synced 2025-01-18 05:12:45 +01:00
5e3e2f4e17
This will never be reliable under high load, without making it unable
to detect real errors. But the test is useful because if we don't
have this test we'll never notice if we break the const-timedness of
our implementation.
So, move the calloc out of the test loop (which seems to make it more
reliable), and then after we've run it, check the 1-minute load
average. Too high, we don't complain about results. It's not
perfect, but it's better.
Running 100 times (-O3) serially gave 100 successes with the following results:
Constant: Within 5% 562-926(832.89+/-73)/1000 times
Non-constant: More than 5% slower 860-990(956.35+/-26)/1000 times
More importantly, if we swap the const and non-const tests, we get
the expected 100 failures:
Non-constant: Within 5% 14-79(41.17+/-14)/1000 times
Constant: More than 5% slower 44-231(111.89+/-33)/1000 times
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
|
||
|---|---|---|
| .. | ||
| test | ||
| address.h | ||
| base58.c | ||
| base58.h | ||
| block.c | ||
| block.h | ||
| chainparams.c | ||
| chainparams.h | ||
| feerate.h | ||
| locktime.c | ||
| locktime.h | ||
| Makefile | ||
| preimage.h | ||
| privkey.c | ||
| privkey.h | ||
| pubkey.c | ||
| pubkey.h | ||
| pullpush.c | ||
| pullpush.h | ||
| README | ||
| script.c | ||
| script.h | ||
| shadouble.c | ||
| shadouble.h | ||
| short_channel_id.c | ||
| short_channel_id.h | ||
| signature.c | ||
| signature.h | ||
| tx.c | ||
| tx.h | ||
| varint.c | ||
| varint.h | ||
These are standard bitcoin manipulation routines which should be provided by any normal bitcoin library in whatever language you choose. The ones here are standalone ones taken from bitcoin core and some I wrote, many taken from bitcoin-iterate and pasted in here.