New Posts New Posts RSS Feed: Devforce & IIS Express & Large query timeouts
  FAQ FAQ  Forum Search   Calendar   Register Register  Login Login

Devforce & IIS Express & Large query timeouts

 Post Reply Post Reply
Author
pompomJuice View Drop Down
Newbie
Newbie
Avatar

Joined: 29-Jul-2010
Location: ZA
Posts: 28
Post Options Post Options   Quote pompomJuice Quote  Post ReplyReply Direct Link To This Post Topic: Devforce & IIS Express & Large query timeouts
    Posted: 03-Jun-2011 at 1:14am
Hi,

IIS Express has some sort of issue with large queries. (~60K+ rows/~30 second query)

There comes a point where they will just time out, and none of your query time-out suggestions work. (ASP.NET Development Server just works) 

Please figure out and make it go away please :)

W
Back to Top
robertg View Drop Down
IdeaBlade
IdeaBlade
Avatar

Joined: 15-Mar-2011
Location: California
Posts: 87
Post Options Post Options   Quote robertg Quote  Post ReplyReply Direct Link To This Post Posted: 03-Jun-2011 at 11:11am
PompomJuice,

I wish I could just make it go away! Unfortunately, it's not a DevForce problem, so I can just provide some advice.

It seems to me that you can approach this in two directions. You can either increase time timeout settings for IIS Express so it can handle the wait, or you can optimize your query so that it doesn't take as long, and you don't get to the timeout.

For speeding up your query, the first thing I would recommend is to take a look at the query performance article in the DRC: http://drc.ideablade.com/xwiki/bin/view/Documentation/query-performance. In particular, you might want to make sure that you're limiting your includes (which give the query an awful lot more work to do), or replace your current query with an asynchronous query, that brings down chunks of data at a time and thus prevents timeout. You may also choose to limit the amount of data you're querying into your entity with an anonymous projection: http://drc.ideablade.com/xwiki/bin/view/Documentation/query-anonymous-projections.

There are other things you could look into-- such as optimizing the underlying database for queries such as the one that you're running-- but I think that the IIS configuration and query performance steps should resolve your problem.

-- Robert
Back to Top
 Post Reply Post Reply

Forum Jump Forum Permissions View Drop Down