chore(docs): change svg benchmark table names
This is done to ease automated table generation through continuous integration pipeline.
|
Before Width: | Height: | Size: 16 KiB After Width: | Height: | Size: 16 KiB |
|
Before Width: | Height: | Size: 13 KiB After Width: | Height: | Size: 13 KiB |
|
Before Width: | Height: | Size: 16 KiB After Width: | Height: | Size: 16 KiB |
|
Before Width: | Height: | Size: 13 KiB After Width: | Height: | Size: 13 KiB |
|
Before Width: | Height: | Size: 15 KiB After Width: | Height: | Size: 15 KiB |
|
Before Width: | Height: | Size: 13 KiB After Width: | Height: | Size: 13 KiB |
|
Before Width: | Height: | Size: 16 KiB After Width: | Height: | Size: 16 KiB |
|
Before Width: | Height: | Size: 13 KiB After Width: | Height: | Size: 13 KiB |
|
Before Width: | Height: | Size: 15 KiB After Width: | Height: | Size: 15 KiB |
|
Before Width: | Height: | Size: 5.7 KiB After Width: | Height: | Size: 5.7 KiB |
|
Before Width: | Height: | Size: 14 KiB After Width: | Height: | Size: 14 KiB |
|
Before Width: | Height: | Size: 5.8 KiB After Width: | Height: | Size: 5.8 KiB |
@@ -16,21 +16,21 @@ The next tables show the operation timings on CPU when all inputs are encrypted:
|
||||
|
||||
### Encrypted/encrypted operations latency
|
||||
|
||||

|
||||

|
||||
|
||||
### Encrypted/encrypted operations throughput
|
||||
|
||||

|
||||

|
||||
|
||||
The next tables show the operation timings on CPU when the left input is encrypted and the right is a clear scalar of the same size:
|
||||
|
||||
### Encrypted/clear operations latency
|
||||
|
||||

|
||||

|
||||
|
||||
### Encrypted/clear operations throughput
|
||||
|
||||

|
||||

|
||||
|
||||
All timings are based on parallelized Radix-based integer operations where each block is encrypted using the default parameters `PARAM_MESSAGE_2_CARRY_2_KS_PBS`. To ensure predictable timings, we perform operations in the `default` mode, which ensures that the input and output encoding are similar (i.e., the carries are always emptied).
|
||||
|
||||
|
||||
@@ -15,21 +15,21 @@ The following tables show the performance when the inputs of the benchmarked ope
|
||||
|
||||
### Encrypted/encrypted operations latency
|
||||
|
||||

|
||||

|
||||
|
||||
### Encrypted/encrypted operations throughput
|
||||
|
||||

|
||||

|
||||
|
||||
The following tables show the performance when the left input of the benchmarked operation is encrypted and the other is a clear scalar of the same size:
|
||||
|
||||
### Encrypted/clear operations latency
|
||||
|
||||

|
||||

|
||||
|
||||
### Encrypted/clear operations throughput
|
||||
|
||||

|
||||

|
||||
|
||||
## Reproducing TFHE-rs benchmarks
|
||||
|
||||
|
||||
@@ -15,21 +15,21 @@ The following tables show the performance when the inputs of the benchmarked ope
|
||||
|
||||
### Encrypted/encrypted operations latency
|
||||
|
||||

|
||||

|
||||
|
||||
### Encrypted/encrypted operations throughput
|
||||
|
||||

|
||||

|
||||
|
||||
The following tables show the performance when the left input of the benchmarked operation is encrypted and the other is a clear scalar of the same size:
|
||||
|
||||
### Encrypted/clear operations latency
|
||||
|
||||

|
||||

|
||||
|
||||
### Encrypted/clear operations throughput
|
||||
|
||||

|
||||

|
||||
|
||||
## Reproducing TFHE-rs benchmarks
|
||||
|
||||
|
||||