1. Load up a channel with a long message history
2. Scroll back and forward in time. Ensure that messages load and that performance seems "good" in relation to past experience on that server. At least make sure that the delay to load messages doesn't seem extreme.
I believe the next-steps of this issue are one of the following:
Decide to push this change into master and let it soak on community-daily
Go with something along the lines of what proposed in the performance channel: So I’m curious if it makes sense to push these changes back to the other get posts methods, assuming we see similar performance gains. Might be a nice win everywhere!
Change merged into 5.14:
Working on 5.13 now.
Change is now merged to 5.13 as well:
It was determined that the soaking these changes did on master were the best test (test server won't have the data needed for a meaningful test). Closing. Release tests not needed, PR labeled.
Closing this off as per Linda's comment.