(cloud) Added running balance cache for ledger

things-to-search-for.txt

@@ -1,8 +1,6 @@
 or-join syntax changed?
-helper to lookup rel db-id
 Make sure no history on ledger
 it looks like there are a bbunch of orrphaned customizations for accounts, breaking indexes
-automatically rebuild search indexes
 ezcater graphql needs search index too
 make sure that temporary ids are set on all new things when using upsert-entity
 Wrap tests around every api call
@@ -12,3 +10,14 @@ Make a different solution for running balance cache
 * Make ledger changes mark as dirty
 * Recompute the cache periodically, somewhat randomly to avoid races
 * Have a background job recompute all at night.
+
+Fix searching
+* indexing should happen more regularly, and just look for changes since last time it was run
+
+Running Balance Cache
+* much simpler now, just make it handle reverts (see TODO)
+** when a journal entry gets reset, you have to recalculate running balance. Could just make it do this globally by marking the earliest journal entry
+
+
+Address memory
+* JVM settings now and in prod