diff options
| author | Pjotr Prins | 2025-07-10 17:43:40 +0200 |
|---|---|---|
| committer | Pjotr Prins | 2026-01-05 11:12:10 +0100 |
| commit | 5db42fb3327d8ee6a5714e83ba756a00e8dcc114 (patch) | |
| tree | 725cb6821aac2ce17b94be57dd7d58c05e0670d0 /topics/data | |
| parent | bc2bcee2057edef6b5a8ebdc5e8e7ff5e2b6f187 (diff) | |
| download | gn-gemtext-5db42fb3327d8ee6a5714e83ba756a00e8dcc114.tar.gz | |
precompute notes
Diffstat (limited to 'topics/data')
| -rw-r--r-- | topics/data/precompute/steps.gmi | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/topics/data/precompute/steps.gmi b/topics/data/precompute/steps.gmi index d22778a..ac03d1a 100644 --- a/topics/data/precompute/steps.gmi +++ b/topics/data/precompute/steps.gmi @@ -2,7 +2,8 @@ At this stage precompute fetches a trait from the DB and runs GEMMA. Next it tar balls up the vector for later use. It also updates the database with the latest info. -To actually kick off compute on machines that do not access the DB I realize now we need a step-wise approach. Basically you want to shift files around without connecting to a DB. And then update the DB whenever it is convenient. So we are going to make it a multi-step procedure. I don't have to write all code because we have a working runner. I just need to chunk the work. +To actually kick off compute on machines that do not access the DB I realize now we need a step-wise approach. Basically you want to shift files around without connecting to a DB. And then update the DB whenever it is convenient. So we are going to make it a multi-step procedure. +We need to chunk the work. We will track precompute steps here. We will have: |