first version of questdb internals

documentation/concept/interval-scan.md

@@ -39,6 +39,7 @@ that falls outside the relevant intervals. However, it's important to note that
 **Interval Scan** does not apply to the results of sub-queries, as the data
 returned from a sub-query is not guaranteed to be in timestamp order.
 
+<!-- this image is used also at the questdb-internals page. Please keep in sync -->
 <Screenshot
   alt="Interval scan."
   height={433}

documentation/concept/partitions.md

@@ -15,6 +15,7 @@ each interval is stored in separate sets of files.
 
 import Screenshot from "@theme/Screenshot"
 
+<!-- This image is used also at the questdb-internals page. Please keep in sync -->
 <Screenshot
   alt="Diagram of data column files and how they are partitioned to form a table"
   height={373}

documentation/concept/storage-model.md

@@ -36,6 +36,7 @@ read by translating the record number into a file offset by a simple bit shift.
 The offset in the column file is then translated into an offset in a lazily
 mapped memory page, where the required value is read from.
 
+<!-- This image is used also at the questdb-internals page. Please keep in sync -->
 <Screenshot
   alt="Diagram showing how the data from a column file is mapped to the memory"
   height={447}
@@ -95,6 +96,7 @@ Data committed by one process can be instantaneously read by another process,
 either randomly (via queries) or incrementally (as a data queue). QuestDB
 provides a variety of reader implementations.
 
+<!-- This image is used also at the questdb-internals page. Please keep in sync -->
 <Screenshot
   alt="Architecture of the storage model with column files, readers/writers and the mapped memory"
   height={596}

documentation/concept/write-ahead-log.md

@@ -125,6 +125,7 @@ A WAL table uses the following components to manage concurrent commit requests:
 - **TableWriter**: updates the database and resolves any out-of-order data
   writes.
 
+<!-- diagram used at the questb-internals page. Please keep in sync -->
 <Screenshot
   alt="Diagram showing the sequencer allocating txn numbers to events cronologically"
   title="The sequencer allocates unique txn numbers to transactions from different WALs chronologically and serves as the single source of truth."
@@ -133,6 +134,7 @@ A WAL table uses the following components to manage concurrent commit requests:
   width={745}
 />
 
+<!-- diagram used at the questb-internals page. Please keep in sync -->
 <Screenshot
   alt="Diagram showing the WAL job application and WAL collect events and commit to QuestDB"
   title="The WAL job application collects the transactions sequencially for the TableWriter to commit to QuestDB."