Skip to content
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

Generate metadata file as output in Cardio SEAL-BFV & Cingulata #14

Open
pjattke opened this issue Aug 6, 2020 · 0 comments
Open

Generate metadata file as output in Cardio SEAL-BFV & Cingulata #14

pjattke opened this issue Aug 6, 2020 · 0 comments

Comments

@pjattke
Copy link
Collaborator

pjattke commented Aug 6, 2020

Add a metadata file (text file) that describes the environment and settings used for the benchmark run.
As there is information that can only be gathered in the container

In-Container Information

This information is only available in the container and we need a script for each combination of (benchmark program, tool).

  • FHE scheme paramters p, q, n
    • see print_parameters(...) in examples.h
  • Ciphertext size (inputs + result)
  • Key size
  • Number of operations (additions, multiplications, relinearizations)
    • this and this could be helpful functions for Cingulata

System / EC2 VM Information

This is information that is not available in the docker container but must be gathered on the EC2 VM.
The script collecting this information is usable for all benchmark programs.

@AlexanderViand What do you think about adding the git commit SHA to the S3 folder name? Would this break something related to the visualization website?

Note to myself - this would require the following change to L43@benchmark.yml:

$(echo $(date +'%Y%m%d_%H%M%S')_$(git rev-parse --short "$GITHUB_SHA"))
@pjattke pjattke changed the title Generate metadata file as output in Cardio SEAL-BFV Generate metadata file as output in Cardio SEAL-BFV & Cingulata Aug 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant