I have a crucial problem of slowness on my website as soon as I overtake several users connected at the same time.
My app is like Tinder (Like/Dislike/Matched), the heart of my app is a HomePage with a repeating group showing the users that can be liked or disliked, which moves to the next one. Inside this repeating group I have another repeating group that refers to a Database with the user publications.
I built the Like/Dislike system and filtered my repeating as much as possible with constraints, used api workflow, etc… to make my app as fast as possible.
I guess the problem comes from the constraints to not show users that have already been liked/displayed that are a “List of Text” with “doesn’t contain”.
The way app works - I think that is the only way it can be structured. You can experiment with Search For Users:until item X. But it will probably be faster only on the first load.
It should be faster with the projects connected to the user directly. Do the changes and let us know if it’s better.