On Thu, Apr 30, 2020, at 7:45 AM, Brian Carpenter wrote:
Any chance a developer can answer Stephen? We are also seeing significant delays working with list members via the REST api and core in our development of Affinity.
We have been discussing this in
https://gitlab.com/mailman/mailman/-/issues/700The crux of the problem is that calculating a Memeber resources is a complex operation and requires several database queries. With my calculation, it takes about 5 database queries per member resource and so if the list of large, the API request can time out.
This isn't straight forward to fix since there isn't any logical bug. We would need to re-architect how the data is loaded from database and Member resource is calculated, possibly loading child resources in the same query to build the Member resource with fewer database queries.
Thanks, Brian
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
-- thanks, Abhilash Raj (maxking)