You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: artifact/README.md
+29-1Lines changed: 29 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -248,7 +248,10 @@ histogram as in the print message: `4 histogram buckets`. Each string e.g.,
248
248
249
249
Lastly, you can run both weighted heavy hitters and attribute based metrics with malicious clients by passing the `--malicious` and a percentage.
250
250
251
-
### Experiments
251
+
252
+
# Experiments
253
+
254
+
## Understanding the configuration files
252
255
Our experiments can be reproduced by using our config files: https://github.com/TrustworthyComputing/mastic/tree/main/src/configs and the values provided in the paper.
253
256
254
257
For instance:
@@ -302,5 +305,30 @@ zipf_exponent = 1.03
302
305
etc. These parameters are sufficient to reproduce all our results -- all our
303
306
experiments in the paper specify the parameters used.
304
307
308
+
## Reproducing Experiments and Figures
305
309
To reproduce our experiments, use the configs from the [configs](./configs/)
306
310
directory and the scripts from the [plots](../plots/) directory.
311
+
312
+
## Troubleshooting
313
+
As mentioned in the **Troubleshooting** section of the [README file](../README.md) file,
314
+
Mastic relies on the [tarpc](https://github.com/google/tarpc) library which has
315
+
a limit on the size of the RPC messages. As such, you might see an error similar
316
+
to the following:
317
+
```shell
318
+
thread 'main' panicked at src/bin/driver.rs:335:
319
+
called `Result::unwrap()` on an `Err` value: Disconnected
320
+
```
321
+
which is caused by the RPC batch sizes.
322
+
323
+
In case you run into this issue, you can fix this easily by reducing the batch
324
+
sizes of either the reports or the FLPs (or both).
325
+
```toml
326
+
add_report_share_batch_size = 1000
327
+
query_flp_batch_size = 100000
328
+
```
329
+
**Note:** this does not affect the online running time, but it affects the
330
+
upload time from the `driver` to the Mastic servers. In other words, this does
331
+
not change the experiments but will make setting up the experiments faster. For
332
+
this reason, most of the provided configs use the default batch sizes, which may
333
+
cause crashes with more clients or bits, but this can be simply resolved by
0 commit comments