Weird timeout when using linq/entity, MVC2

Question

I've just randomly started getting this issue, and previously it has been fine up until tonight. I do not want to touch the timeout stuff, I believe it's not needed.

It's a simple query.

{"Timeout expired.  The timeout period elapsed prior to completion of the 
operation or the server is not responding."}

Here is the code causing the timeout..

   var post = (from p in con.blog_posts 
                    orderby p.post_dt descending 
                    select p).First();

Can anyone think of any crevices I should check to try an resolve this?

edit: I can connect to the server with management studio and it is up..

You say 'it's been fine up until tonight' - what changed tonight? Did the code change, did you add more data, did anything at all change? — Kirk Broadhurst
– Kirk Broadhurst, Commented Aug 11, 2011 at 3:17
The query doesn't timeout and works flawlessly when it's ran from a server at work.. I don't really understand maybe it has to do with a connection issue I'm at school at the moment... — jr3
– jr3, Commented Aug 11, 2011 at 3:36

saus · Accepted Answer · 2011-08-11 03:08:31Z

1

you could avoid the sort:

var post = 
    from p in con.blog_posts
    where p.post_dt == con.blog_posts.Max(post=>post.post_dt) 
    select p

answered Aug 11, 2011 at 3:08

saus

2,19417 silver badges15 bronze badges

Sign up to request clarification or add additional context in comments.

8 Comments

Kirk Broadhurst Over a year ago

I believe the order by will be at least as fast, if not faster, since it'll be translated into SQL and executed in the database. I do not know whether the Max will be translated into a single SQL statement along with the select - and even if it is, it won't be quicker than a simple SELECT TOP 1 ORDER BY

saus Over a year ago

yar good point, I tested in linqpad afterwards and you are correct - I'll delete this post

saus Over a year ago

hmm...actually I tested again five times for each query: the Max method was slightly faster on average (~540ms vs ~640ms for 2.2M rows) - but given the OPs comment that there are only 3 rows, this is clearly not the solution.

jr3 Over a year ago

I believe the issue is because I'm behind my school's connection, when ran from another connection it's fine...

Kirk Broadhurst Over a year ago

@saus I find it hard to believe the order by would be slower when the table is indexed. And you would never order by 2M rows without an index.

|

Kirk Broadhurst · Accepted Answer · 2011-08-11 03:16:34Z

1

Are other database queries working as expected? Go to your database and run that query and see how long it takes to return. Try to run the exact query (capture it in SQL Profiler). This will tell you if your database is simply performing slowly for this query, or whether it's another issue.

My first guess would be that you don't have an index on the post_dt column. Trying the query directly in SQL will prove or disprove this. If the query takes a long time to run, add a nonclustered index on that column and retry.

answered Aug 11, 2011 at 3:16

Kirk Broadhurst

28.9k20 gold badges111 silver badges179 bronze badges

2 Comments

jr3 Over a year ago

the SQL query performance is great, this table only has 3 records.

Kirk Broadhurst Over a year ago

You ran the same query that is generated from your application, captured in SQL Profiler or similar?

Collectives™ on Stack Overflow

Weird timeout when using linq/entity, MVC2

2 Answers 2

8 Comments

2 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

8 Comments

2 Comments

Your Answer

Sign up or log in

Post as a guest

Related