From 603dd9fc7136d7b1b7c86b6fa8d29e07f5a891b8 Mon Sep 17 00:00:00 2001 From: Jos de Bruijn Date: Wed, 16 Nov 2016 12:11:58 -0800 Subject: [PATCH] added explanation of scale factor --- .../features/in-memory/benchmark-order-processing/README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/samples/features/in-memory/benchmark-order-processing/README.md b/samples/features/in-memory/benchmark-order-processing/README.md index b04f1fc5..6b232571 100644 --- a/samples/features/in-memory/benchmark-order-processing/README.md +++ b/samples/features/in-memory/benchmark-order-processing/README.md @@ -31,7 +31,8 @@ Sample order processing workload that can be used for benchmarking transactional |Products |10 | |PurchaseCriteria |1 | |Fulfillment|0| - + + - The *scale factor* is a number that governs the actual database size for a given run of the workload. The actual row count for a given table is `[scale factor * weight * 10,000]`. For example, with scale factor 5, the Products table has 5 * 10 * 10,000 = 500,000 rows. 2. Run the stored procedures using the following mix.