The PALISADE-CPU backend is a Reference backend engine for HEBench which is a shared library that implements the required functions specified in either the hebench::APIBridge or hebench::cpp wrapper. It is intended only as a reference on how to implement a PALISADE backend for HEBench and it is not fully optimized for performance.
What types of changes does your code introduce to the HEBench PALISADE Reference Backend?
Put an x in the boxes that apply
[ ] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Update (if none of the other choices apply)
Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.
Proposed changes
Full set of benchmarks ( == added with this PR): 1. Element-wise Add | BFV | Latency 2. Element-wise Add | CKKS | Latency 3. Element-wise Add | BFV | Offline 4. Element-wise Add | CKKS | Offline 5. Element-wise Mult | BFV | Latency 6. Element-wise Mult | CKKS | Latency 7. Element-wise Mult | BFV | Offline 8. Element-wise Mult | CKKS | Offline 9. Dot Product | BFV | Latency 10. Dot Product | CKKS | Latency 11. Dot Product | BFV | Offline *12. Dot Product | CKKS | Offline
Types of changes
What types of changes does your code introduce to the HEBench PALISADE Reference Backend? Put an
x
in the boxes that applyChecklist
Put an
x
in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.Further comments
N/A