diff options
author | Pjotr Prins | 2023-03-24 06:59:16 +0100 |
---|---|---|
committer | Pjotr Prins | 2023-03-24 06:59:16 +0100 |
commit | 0c679f8f62f769b380f4d407cbf3cc087cfec86a (patch) | |
tree | b613012a6033bc64fab93be383533476c3891a3b /topics/systems/mariadb | |
parent | 88bfad504995070d8c79cd27111372a1960be233 (diff) | |
download | gn-gemtext-0c679f8f62f769b380f4d407cbf3cc087cfec86a.tar.gz |
Note on size of ProbeSetXRef
Diffstat (limited to 'topics/systems/mariadb')
-rw-r--r-- | topics/systems/mariadb/precompute-mapping-input-data.gmi | 2 |
1 files changed, 2 insertions, 0 deletions
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. |