From a970d8472c8c3e2f5a3ea9fdeaf1e6b6898c88a0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Juli=C3=A1n=20Gonz=C3=A1lez=20Calder=C3=B3n?= Date: Wed, 20 Nov 2024 16:44:05 -0300 Subject: [PATCH] Restore readme --- README.md | 16 +--------------- 1 file changed, 1 insertion(+), 15 deletions(-) diff --git a/README.md b/README.md index 2268992a..6215aafa 100644 --- a/README.md +++ b/README.md @@ -137,20 +137,6 @@ Once you have done this, you can use the plotting scripts: - `python ./plotting/plot_compilation_memory_trend.py native-logs vm-logs`: Size of the compiled native and casm contracts, by the sierra contract size. - `python ./plotting/plot_compilation_time.py native-logs`: Native compilation time, by contract class - `python ./plotting/plot_compilation_time_trend.py native-logs vm-logs`: Native and Casm compilation time, by the sierra contract size. +- `python ./plotting/plot_execution_time.py native-logs vm-logs`: Plots the execution time of Native vs VM, by contract class. - `python ./plotting/plot_compilation_time_finer.py native-logs`: Native compilation time, with fine-grained stage separation, by contract class. -If you want to plot the execution time comparison you must first parse the logs with a different script. - -```bash -python ./plotting/parse_execution_time.py native-logs -python ./plotting/parse_execution_time.py vm-logs -``` - -This will output new files `native-logs-execution` and `vm-logs-execution`. Then you can plot them with: - -```bash -python ./plotting/plot_execution_time.py native-logs-execution vm-logs-execution plot.png -``` - -The execution plog will be saved to `plot.png`. -