Revert default batch size for server side loader

Author: joshua-spacetime

tools/tpcc-runner/README.md

@@ -130,7 +130,7 @@ cargo run --release -p tpcc-runner -- load \
 
 `--batch-size` still matters for `load`, but it now controls the server-side
 chunk size for phases like items, stock, and orders instead of the number of
-rows pushed over the websocket by the client. The default is `10000`.
+rows pushed over the websocket by the client. The default is `500`.
 
 If a server-side load fails, the current `load` command does not resume it
 automatically. Resume each affected database manually with:
@@ -257,7 +257,7 @@ timeout_secs = 30
 num_databases = 1
 warehouses_per_database = 1
 load_parallelism = 1
-batch_size = 10000
+batch_size = 500
 reset = true
 
 [driver]

tools/tpcc-runner/src/config.rs

@@ -7,7 +7,7 @@ use std::path::{Path, PathBuf};
 
 use crate::protocol::DriverAssignment;
 
-const DEFAULT_LOAD_BATCH_SIZE: usize = 10_000;
+const DEFAULT_LOAD_BATCH_SIZE: usize = 500;
 
 #[derive(Debug, Parser)]
 #[command(name = "tpcc-runner")]
@@ -452,7 +452,7 @@ mod tests {
     }
 
     #[test]
-    fn load_args_default_batch_size_is_10000() {
+    fn load_args_default_batch_size_is_500() {
         let args = LoadArgs {
             connection: ConnectionArgs::default(),
             num_databases: Some(1),