diff --git a/DEBUG_DB.md b/DEBUG_DB.md
index 6f1b7d0949f3a26dc43db6ce513842fda2f5e186..6d701744df77f8ee8e5258f987b62d94af10b862 100644
--- a/DEBUG_DB.md
+++ b/DEBUG_DB.md
@@ -1,5 +1,5 @@
 <!--
-SPDX-FileCopyrightText: Copyright 2021, 2023 Arm Limited and/or its affiliates <open-source-office@arm.com>
+SPDX-FileCopyrightText: Copyright 2021, 2023, 2025 Arm Limited and/or its affiliates <open-source-office@arm.com>
 
 SPDX-License-Identifier: Apache-2.0
 
@@ -32,7 +32,7 @@ command generation in its internal Debug Database.  The database tracks the data
 transformations through the following states:
 
 - Creation of Source operators - these operators are created from the source
-  representation, in this case the original TFLite file
+  representation, in this case the original network
 - Creation of Optimised operators - these are the operators that result from
   optimising the source operators.  They may be the source operators repeated,
   or substitute operators inserted by the optimiser
@@ -69,17 +69,24 @@ CDATA payload tag. The first row of the table contains column headers.
 <table name="source"><![CDATA[ "column0", "column1", "column2", ... ]]></table>
 ```
 
-There currently are 4 named tables.
+There currently are 5 main types of tables.
 
-- `source` - Table of TFLite operators from the source file.
+- `source` - Table of operators from the source file.
 - `optimised` - Table of optimised operators generated by vela
 - `queue` - Table of command queue offsets
 - `cmdstream` - Table describing properties of one or more command streams
-
-The tables reference each other through the following connections: the `queue`
-table is linked to the `optimised` table through the *optimised_id* and the
-command stream table through the *cmdstream_id*.  The `optimised` table is in
-turn linked to the `source` table through the *source_id*.
+- `perf` - Tables of scheduled operator performance info. Note, the perf tables
+  are only enabled when compiling for Ethos-U85, or when using the
+  `--debug-force-regor` flag
+
+The tables reference each other through the following connections:
+* The `queue` table is linked to the `optimised` table through the
+*optimised_id* and the `cmdstream` table through the *cmdstream_id*. It is also
+linked to the tables prefixed with `perf` through the *scheduled_id*
+* The `optimised` table is in turn linked to the `source` table through the
+*source_id*
+* The tables prefixed with `perf` are linked to the `optimised` table through
+the *optimised_id* in the table explicitly called `perf`.
 
 ## Ordering