I was not able to reproduce the behavior you stated.

Here is my test solution: uploads/892/T12223_.zip

 

Please provide a reproducible test case so we can further investigate this issue.

 

Silvio.

 

I'm still working on reproducing the issue.

Any update on this one?

This is a critical issue in our part and we need to fix it as early as possible.

Thanks,

Von

 

I'll try to reproduce the behavior here so we can further investigate.

 

Silvio.

We're expecting a huge amount of records to query so querying it once will not work for us.

 

Have you tried executing the Query only once? i.e. customers.Execute() / stores.execute() - you might also execute them asynchronously.

 

In your for statement you are issuing a query against the datasource for each page. Since you are loading everything anyway, you my as well execute it against the data already loaded in the cache.

 

That might help.

 

sbelini.

 

Just want to follow up this..

Thanks,

Von

I can't provide a database but let's assume that my DB schema and indexes are all in good shape.

Then I have this kind of query (Disregard the logic here):

Another is there are no direct relationship between tables and models.

var remainder = 0;

var count = stores.Count();

var pageSize = 50;

for (int x =0; x <= pageCount ; x++)

{

    var pagedStores = stores.OrderBy(o => p.StoreID).Skip(x * pageSize).Take(pageSize);

foreach(var store in pagedStores)

{

Console.WriteLine("Store ID: {0}", store.StoreID);

}

}

Example my count is 50k records, so I will have 1k page..

What happen in this query, every page it adds approximately 1 second delay.

So meaning the first page is 1 second, second is 2 second delay and so on and it will come to a point that it will time out...

What do you think is the problem with this approach or do you have any  solution that can improve our query?

Note: We already used the EntityQueryPager<T> but still no luck..

We also try juggling some of the QueryStrategy but also failed.

Thanks,

Von