@@ -61,6 +61,21 @@
 </pre>
 The 'messagefile' contains the log message, the 'filefile' lists the revisions in the manifest by id, and with path in the workspace. The parents are the ids of the parent manifests. The result of the command is the id of the new manifest.
 <br>
 Note: We have already commands for the put and deltify operations, albeit undocumented, in the set of test commands.
 </li>
+</ul>
+
+Miscellaneous:
+<ul>
+<li>Go over the SQL statements and check that they have good query plans
+</li>
+<li>Go over the SQL statements and add comments where they are non-trivial.
+</li>
+<li>Currently some passes take quite a bit of time when their actual operation is already complete. It seems that sqlite is heavily working on committing a lot of changes (Most passes are wrapped into a single transaction). Consider ways of speeding this up.
+<ul>
+<li>Do our own transaction management? So that we can commit every X changes?.
+</li>
+<li>Should we disable synchronous operation? The state database is not that critical, i.e. it can always be regenerated. On the other hand, being able to be sure that we can restart from the interrupted pass is nice, and not possible if we got it corrupted by asynchronous operation. <b>Tabled for now, this is not yet critical</b>
+</li>
+</ul>
 </ul>