Presence List/Fetch Override: Too many unnecessary database calls, 4+ calls per join, how to fix?

Thanks for the response. Last week, I had actually figured out how to do just what you described: Help: Check My Work - Fetching Basic Presence Details With Ecto - Advice Welcome - #14 by John-Goff , to simply not do a DB call if the user list is empty.

That didn’t solve the issue entirely, because in the join, there are two duplicate calls to fetch all user details for all of users, plus one call to fetch the user details for the one user joining, and in the leave, there is an unnecessary call to fetch user details for a user who is about to leave the room, which doesn’t make sense since they are leaving the room anyways, why grab their details.

It would be nice if there was just one fetch - after someone joins the room (so both the room and new user get the full list of users in the room) - no fetching when a user leaves. How would I configure that?