sweet: make the default run -count more reasonable

The default of 25 will cause benchmarks to run for an extremely long
time. Use 10 instead, which is what we use on the builders.

Change-Id: Ia520f78c62853d719a8443c051dd8b1595f1d9b9
Reviewed-on: https://go-review.googlesource.com/c/benchmarks/+/449295
Reviewed-by: Keith Randall <khr@golang.org>
Reviewed-by: Keith Randall <khr@google.com>
Run-TryBot: Michael Knyszek <mknyszek@google.com>
TryBot-Result: Gopher Robot <gobot@golang.org>
diff --git a/sweet/cmd/sweet/run.go b/sweet/cmd/sweet/run.go
index f683633..27bcc80 100644
--- a/sweet/cmd/sweet/run.go
+++ b/sweet/cmd/sweet/run.go
@@ -152,7 +152,7 @@
 	f.StringVar(&c.runCfg.perfFlags, "perf-flags", "", "the flags to pass to Linux perf if -perf is set")
 	f.BoolVar(&c.pgo, "pgo", false, "perform PGO testing; for each config, collect profiles from a baseline run which are used to feed into a generated PGO config")
 	f.IntVar(&c.runCfg.pgoCount, "pgo-count", 0, "the number of times to run profiling runs for -pgo; defaults to the value of -count if <=5, or 5 if higher")
-	f.IntVar(&c.runCfg.count, "count", 25, "the number of times to run each benchmark")
+	f.IntVar(&c.runCfg.count, "count", 10, "the number of times to run each benchmark")
 	f.BoolVar(&c.quiet, "quiet", false, "whether to suppress activity output on stderr (no effect on -shell)")
 	f.BoolVar(&c.printCmd, "shell", false, "whether to print the commands being executed to stdout")