From 0c679f8f62f769b380f4d407cbf3cc087cfec86a Mon Sep 17 00:00:00 2001
From: Pjotr Prins
Date: Fri, 24 Mar 2023 06:59:16 +0100
Subject: Note on size of ProbeSetXRef

---
 topics/systems/mariadb/precompute-mapping-input-data.gmi | 2 ++
 1 file changed, 2 insertions(+)

(limited to 'topics/systems')

diff --git a/topics/systems/mariadb/precompute-mapping-input-data.gmi b/topics/systems/mariadb/precompute-mapping-input-data.gmi
index 361d495..733faea 100644
--- a/topics/systems/mariadb/precompute-mapping-input-data.gmi
+++ b/topics/systems/mariadb/precompute-mapping-input-data.gmi
@@ -112,3 +112,5 @@ From this exercise we can conclude:
 * No significance score is computed (needs permutations)
 
 Rob voiced a wish to retain all scores (at least those above 1.0). This is not feasible in mariadb, but we can retain GEMMA output if stored efficiently.
+
+ProbeSetXRef is pretty small, currently @5.6Gb and 48,307,650 rows, so we could decide to add columns to track different mappers.
-- 
cgit v1.2.3