1fifoto
commented
2 months ago Taken from Issue 441
medium priority
Performance concerns: compression spring demo10 is my recommendation for a test case to reproduce the performance problem.
From June 23 3:30pm PST Slack entry: Performance testing: A quick review of demo sessions discovered that in compression spring demo10, the transition from page 09 to page 10 of 15 contains a search that runs for 70 iterations. I set up my two VMs side-by-side. The left side was the branch 441 development environment (v5.0dev). The right side was the master branch development environment (v4.6dev). I used the stopwatch app of my smartphone to do the timing. The average page 9 to 10 transition time for branch 441 was roughly 21 seconds. The average page 9 to 10 transition time for the master branch was roughly 1.5 seconds. If you want to run this test many times and eliminate having to hit "Next" a bunch of times, it would be pretty easy to create a stripped-down version of the demo10 script. Just a side observation ... many operations (demo page transitions) in branch 441 are perceptibly slower than their equivalents in the master branch. So, my guess is that the root performance issue is pretty low-level and impacts a lot more than just Search. Using a Search that requires a large number of iterations makes for a good test case because it makes the differences easy to see. Also, Search is so fundamental to the app, it provides confidence that we are not wasting time on some rare corner case. Let me know if you think that I can do more along these lines.
grumpyinca
Possibly replace/regress Redux Tool Kit (RDK) to use original Redux.