Obeya's server runs on one thread, and several reads it repeats on every change, every Koordinator command and every check of the shared pages used to go through whole tables. The longer Obeya was in use, the longer every page and the phone froze while they ran. These reads now use indexes or keep what they read up to date, and the remaining synchronous file and process calls are off the server's thread. Over a history ten times today's, each of these rounds now costs about as much as rebuilding one canvas view, where some cost over two hundred before. A load test and a guard against new synchronous calls keep it that way.
Obeya no longer slows down as its history grows
Shared by Daniel Sadilek on November 9, 2026