Ian Goldberg 2840ccb8b8 Be able to run the tests for each of the figures separately | il y a 10 mois | |
---|---|---|
.. | ||
README.md | il y a 1 an | |
generate_raw_data_bs.sh | il y a 1 an | |
generate_raw_data_bs_const_db.sh | il y a 1 an | |
generate_raw_data_heap.sh | il y a 1 an | |
generate_raw_data_heap_const_db.sh | il y a 1 an | |
generate_raw_data_reads.sh | il y a 1 an | |
generate_raw_data_reads_const_db.sh | il y a 1 an | |
generate_raw_data_reads_ssh.sh | il y a 1 an | |
parse_logs | il y a 1 an | |
repro | il y a 10 mois |
cd ../docker
./build-docker
./start-docker
(This will start three dockers, each running one of the parties.)./set-networking 30ms 100mbit
cd ../prac
Run the reproduction script ./repro
with one of the following arguments:
./repro test
: Run a short (about 30 seconds) "kick-the-tires" test.
You should see output like the following:
Running test experiment...
Wed Nov 1 03:59:19 PM EDT 2023: Running 16 1 ...
# Test output
CircuitORAMOnln read 16 1 6.289 s
CircuitORAMOnln read 16 1 355.3125 KiB
CircuitORAMTotl read 16 1 7.145 s
CircuitORAMTotl read 16 1 2478.5 KiB
# End test output
The last four lines are the output data points, telling you that a Circuit ORAM read test on an ORAM of size 216, with a network configuration of 1us latency and 100gbit bandwidth, performing 1 read operation, took 6.289 s of online time and 7.145 s of total (precomputation plus online) time, and 355.3125 KiB of online bandwidth and 2478.5 KiB of total bandwidth. If you've run the test before, you will see means and stddevs of all of the output data points. When you run it, the time of course will depend on the particulars of your hardware, but the bandwidths used should be exactly the values quoted above.
./repro all numiters
: Run all of the tests, doing numiters
iterations of each.Stop the docker:
../docker/stop-docker