diff options
| author | BonfaceKilz | 2021-10-18 12:47:16 +0300 |
|---|---|---|
| committer | BonfaceKilz | 2021-10-18 12:50:58 +0300 |
| commit | aa89f63f991d5bfec52cf8de183eca9df42b6079 (patch) | |
| tree | 297766d4a2ab15849a67a8c3844a2fb6ca313c1f | |
| parent | 5804b4cd181176fb3bbbc29d9d741fd8befa84a3 (diff) | |
| download | gn-gemtext-aa89f63f991d5bfec52cf8de183eca9df42b6079.tar.gz | |
Update notes on slow correlations
| -rw-r--r-- | issues/slow-correlations.gmi | 14 |
1 files changed, 14 insertions, 0 deletions
diff --git a/issues/slow-correlations.gmi b/issues/slow-correlations.gmi index 30cd980..955800c 100644 --- a/issues/slow-correlations.gmi +++ b/issues/slow-correlations.gmi @@ -91,3 +91,17 @@ Something cool that Alex pointed is an interesting "manual" testing mechanism which he can feel free to try out: Separate the actual "computation" and the "pre-fetching" in code. And see what takes time. + +# Notes + +#### Mon 18 Oct 2021 12:42:17 PM EAT + +Atm GN2 is un-usable for Rob for basic tours and show-and-tells, and +it is a persistent problem that is getting worse the more he +complains. Correlation is slower than it was ever before; and search +is broken. For a simple search of 10,000 phenotypes, it takes a lot of +time to compute. + +According to Rob, GN1 does not rely on a cache. Instead it is +computing from a materialized view of the database that is +intentionally designed for a fast web service.
\ No newline at end of file |