From d81d02f11d22c85b98cab98ebf4caae6f1cfc049 Mon Sep 17 00:00:00 2001
From: Andrew Noyes <andrew@weaselab.dev>
Date: Tue, 5 Mar 2024 17:09:28 -0800
Subject: [PATCH] Don't gc in write benchmarks

This makes it easier to evaluate the claim that "point writes are
comparable to point reads" in performance, which should be the case.
---
 Bench.cpp | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/Bench.cpp b/Bench.cpp
index 6e4fe02..20b66a9 100644
--- a/Bench.cpp
+++ b/Bench.cpp
@@ -192,7 +192,6 @@ void benchConflictSet() {
     bench.run("point writes", [&]() {
       auto v = ++version;
       cs.addWrites(writes.data(), writes.size(), v);
-      cs.setOldestVersion(version - kMvccWindow);
     });
   }
 
@@ -213,7 +212,6 @@ void benchConflictSet() {
     bench.run("prefix writes", [&]() {
       auto v = ++version;
       cs.addWrites(writes.data(), writes.size(), v);
-      cs.setOldestVersion(version - kMvccWindow);
     });
   }
 
@@ -234,12 +232,13 @@ void benchConflictSet() {
     bench.run("range writes", [&]() {
       auto v = ++version;
       cs.addWrites(writes.data(), writes.size(), v);
-      cs.setOldestVersion(version - kMvccWindow);
     });
   }
 
   bench.batch(1);
 
+  cs.setOldestVersion(version - kMvccWindow);
+
   {
     bench.run("monotonic increasing point writes", [&]() {
       auto v = ++version;