Open fosterlynn opened 7 months ago
A note: Today I have a plan with 9 processes and 45 commitments, to save it (the first time) and bring it back was close to 20 minutes. It took a lot longer to bring it back. My impression is it is taking longer to bring a plan back the more plans I add.
From testing today: I added another instance to the network seed I have been using for a week (5 instances), this one from a new release. It was unbearably slow, and I basically could do almost nothing, even some simple lists would not load. Tested on another machine, it was reasonably fast. Installed the same new release on my machine with a new seed, and it was also reasonably fast! Note all the instances of the slow network are on my machine; and I run only one at a time. (There might be one instance hiding on another machine, but it never synced the first time, and then part way through testing today, I removed it. Timing unclear related to anything else. Probably can disregard.)
Another data point: I tested using a seed that has 3 or 4 "nodes", all living on my computer. Time to bring up a plan to edit: 12 minutes. I tested with a new seed, with approximately the same data, time to bring up a plan to edit: 2.5 minutes. Need to experiment with nodes being on different computers to see if that matters.
Next data point: Laura had a timeout after the plan saved, when it was trying to reload. She has a Mac.
This means we do need to take steps on the performance, it isn't just my computer. I took off the "lower priority" tag.
Suggestions so far:
P.S. I couldn't figure out how to get the console in her Mac.
After some discussion, we are thinking to try combining the Plan - Process - Commitment - Agreement into one DNA, and see if the performance of saving, but more importantly loading, the plan improves.
Huge progress made, taking this out of this milestone. Leaving open because there has been discussion of other things we can do.
Both general and in specific places. For discussion, and to keep in mind, not to set aside time yet before getting the features working.