Brandon Trautmann

> However now I found out the culprit was probably that I was running the app in debug mode. If I run it in profile mode, the performance is already...

Yeah I've checked the CPU Profiler and don't see anything obvious. Majority of the time was spent on isolate communication but that is about typical even before introducing drift because...

Just following up--I did a very rudimentary "Stopwatch test" and printed the elapsed time between when the query is invoked and when the function returns and it's about 5-6s which...

> What ends up happening with the result of the calculations? Is there any reason the calculations need to be done in dart instead of sqlite? I actually had hopes...

> Huh yeah that does seem odd - optimizing a slow query is one thing, but I overlooked that the primary issue is UI jank despite using isolates 😅 >...

> I'll try to reproduce this as well, but it'll probably take me until the end of the week. > > > Mapped to domain models at 5727ms (0.3% of...

OK that's super helpful, and has returned some interesting data. I slightly tweaked the print message because the elapsed time was getting pushed outside the debug message length: ```dart if...

Yeah this is pretty wild. I used an sqlite viewer to view the DB and everything looks good. The same SQL statement run from that viewer runs in ~10ms.

OK Update: I commented out the query for the transactions table and the one for the above table began executing much faster, so it was a red herring that it...

OK I appreciate you pointing me back to the CPU Profiler, as there are some interesting things happening there: **JoinedSelectStatement._columnsWithName**  **JoinedSelectStatement._mapRow**  **InsertStatement.createContext**  The last of these jumps...