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
Please refer to [esrally CLI reference](https://esrally.readthedocs.io/en/stable/command_line_reference.html) for more details.
281
281
282
+
## Replaying an existing corpus
283
+
If the `use-corpus-at-path` flag is used, the corpus will not be generated but rather loaded from the file passed as value of the flag.
284
+
If the `rally-track-output-dir` flag is used alongside the `use-corpus-at-path` flag, the persisted rally track will reference a copy of the existing corpus saved in the directory passed as value of the `rally-track-output-dir` flag.
285
+
286
+
## Loading a package from registry
287
+
If the `package-from-registry` flag is used, the package installed in Kibana and its assets referenced in the track will be loaded from registry. The format of the flag value is `%packageName%-%packageVersion%`.
288
+
You still need to be in the root of the local package when running the command in order to read the benchmark scenario (`benchmark` flag).
289
+
290
+
## Running benchmark with the same corpus against different versions of a package
291
+
If you use both the `use-corpus-at-path` flag and the `package-from-registry` flag multiple times, you can run benchmark with the same corpus against different versions of the same package, just updating the package version in the relevant flag between executions.
292
+
If you add the `rally-track-output-dir` flag and the `dry-run` flag, you can persist multiple rally tracks with the same corpus for different package versions, using different values for the `rally-track-output-dir` flag.
0 commit comments