Further investigation of the ToDynamicListAsync method shows the new module uses System.Linq.Dynamic.Core v 1.2.18 as opposed to the latest 1.3.4.
Upgrading the package fixed the issue.
This was a new module created by the latest version of ABP Suite. V1.2.18 is marked as Vulnerable. This may need to be fixed in the Project Templates.
I was able to get it working with your workaround. This however did not show the cause of the problem, so I started stepping back one change at a time.
I removed the AddTransient code first, then I reverted back to the PagedResult return type.
I reverted back to the old code in indexcshtml.cs and in the end I was left with the following change.
In the end my only changes were:
var lookupData = await query.PageBy(input.SkipCount, input.MaxResultCount).ToDynamicListAsync<CustomTestCategory>();
to
var lookupData = await query.PageBy(input.SkipCount, input.MaxResultCount).ToListAsync();
and 2) added
using Microsoft.EntityFrameworkCore;
I think the issue here is around this method ToDynamicListAsync
This became and issue after I added a Module to the solution that was originally built with 6.0.2 and upgraded to 7.3.2
The error is resolved, but the issue still needs investigation as this will happen with any new entities created.
I have an API using the same Redis server serving requests at 100ms. I am aware that in a production environment the cache should be hosted closer.
I am absolutely certain this is not the cause of the 35s return time for 12 objects. I am returning a list of countries with 4 properties. I only have 12 countries in the list. It is not a process heavy call, It returns 12 countries in 35 seconds. This happens on first load after which it comes down to 10s. Leaving it a while and returning to the page, the request is back up to 30+ seconds.
I am not sure if there are additional connection checks that could be the cause or whether it may be the storing of data from the database into the cache.