Thank you @paul-grist
I install grist on my old synology NAS with HDD not possible install SSD for cash.
- Yesterday I encountered the fact that when starting the background indexing of disks, noticeable delays began. So I thought that this could be compensated by REDIS.
- If you use grist for IoT logging (I currently have about 1200000 records in one sqlite table per quarter), then in the future if this is translated into grist I think how to speed up performance with minimal way.
Grist and as NocoDB is maximum fastest way create Headless CMS (much faster than Strapi or Directus). But NocoDB loses to Grist in data filling speed (thanks Excel-like spreadshets and widgets) and formulas, but wins in that it can act as an interface for almost any database (like as phpmyadmin). If using Grist backend and as single source data for many project from one document I also want to understand how to use Grist efficiently as possible.
But unfortunately, I have not yet found a way to read / write data directly to a table without using the REST API .grist (sqlite). Only manual import and export of records between the actual sqlite (or mysql) DB and self-hosted Grist App, like as stream endpoint.