-
Notifications
You must be signed in to change notification settings - Fork 12
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
Benchmark message handling #455
base: main-gnosis-merge
Are you sure you want to change the base?
Conversation
The tests use the eon instead of the keyper config index in the eon fields of messages. They also prevented messages with duplicate identity preimages which are used in Shutterized Gnosis Chain.
This simplifies the tests. We use the underlying EonKeys struct instead. The only functionality we lose is automatically generating a new eon key after a set number of identity preimages. However, we don't cycle through eon keys in production anyway.
Shared preparation is done in dedicated setup functions. Key share benchmarks come in two flavors, first and second. First benchmarks the first arriving share, second the second. The idea is that the second results in a decryption key being generated. The first doesn't have enough key material to do so yet.
I had to start a local postgres instance in order for this to run:
Then I had to set an environment variable:
|
Are these results comparable to what you are seeing?
|
Yes, for a few hunderd identity preimages or less. If I increase the number to 500 - 1000 it goes way up. Note that you also have to increase |
that doesn't sound linear. |
okay, there is definitely something odd going on.
|
it turns out, the benchmark wasn't looping. that is fixed now. |
To run them try the following commands: