Status quo
Currently theget_queryset simply adopted the definedprefetch_related andselect_related definitions. But there are still some existing bottlenecks:

Scenario: No include parameter
Given is: The used serializer has aResourceRelatedField and no include parameter is used.
For that case no predefiniedprefetch_related definition is used.
But theResourceRelatedField needs allids from the relation, so it will trigger the db to get it.

Solution: No include paramter
My current solution is to define conditionalprefetch_related definitions inside theget_queryset() on myviews.
Something like

defget_queryset(self):qs=super().get_queryset()include=self.request.GET.get("include",None)ifnotincludeor"fieldName"notininclude:qs=qs.prefetch_related(Prefetch("field_name",queryset=Model.objects.only('id'))returnqs

Without theprefetch_related definition it leads into the describedm*(n+1) problems

But there is another point. The code below prefetches in any case. But if the api is called withsparse fieldsets and the related field is not part of the request, the prefetching is not needed.

So it need another logic to get the fields parameters and analyze them against the prefetching logic. Something like:

fields=self.request.GET.get("fields[ResourceName]","").split(',')iffieldsand"fieldName"infields:# do prefetchingelse:# do not add default prefetching

So i think this is a general problem which hits every view with aResourceRelatedField, for that it would be worth it to add some logic to the core package to handle this.