-
Notifications
You must be signed in to change notification settings - Fork 147
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
Doc/restrictions #1150
base: main
Are you sure you want to change the base?
Doc/restrictions #1150
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Benchmark
Benchmark suite | Current: ca3fb40 | Previous: 87b9f0e | Ratio |
---|---|---|---|
v0 PBS table generation |
61789832 ns/iter (± 820892 ) |
61613628 ns/iter (± 294876 ) |
1.00 |
v0 PBS simulate dag table generation |
39702895 ns/iter (± 376924 ) |
39150973 ns/iter (± 535820 ) |
1.01 |
v0 WoP-PBS table generation |
52363948 ns/iter (± 1928283 ) |
52288912 ns/iter (± 374626 ) |
1.00 |
This comment was automatically generated by workflow using github-action-benchmark.
655172d
to
af46cf4
Compare
ca3fb40
to
53e7979
Compare
53e7979
to
20b5377
Compare
|
||
Concrete provides a way to ensure that a compilation is going to yield compatible crypto-parameters, thanks to _restrictions_. Restrictions are going to restrict the search-space walked by the optimizer to ensure that only compatible parameters can be returnedyielded. As of now, we support two major restrictions: | ||
|
||
+ __Keyset restriction__ : Restricts the crypto-parameters to an existing keyset. This restriction is suited for users that already have a module in production, and want to compile a compatible module. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't mention use-case here IMO, above all the second one as it's really hacky to have an other hardware
keyset_restriction=restriction | ||
) | ||
restricted_keyset_info = restricted_module.keys.specs.program_info.get_keyset_info() | ||
assert big_keyset_info == restricted_keyset_info |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe add a reuse of a keyset generated from the Big module into the Small one.
Let's wait a review from @yuxizama |
No description provided.