Hi Bo,

I have no problems at all using (some really complex) Where statements myself. Did you try only using the Where statement, without first ordering and the rest? I can imagine the problem is related to the stacking of operations, although I do not know how the Where method actually works. I would suggest performing the Where statement first, and after that order the result.

Cheers, Bert

Bo,

I usually take a step in between to avoid having to work with dates in where clauses

var contest = contests.Children
  .Select(node => new { 
    Node = node, 
    StartDate = DateTime.Parse(node.GetPropertyValue("startDate")), 
    EndDate = DateTime.Parse(node.GetPropertyValue("endDate"))
  })
  .Where(item => item.StartDate <= DateTime.Now && DateTime.Now <= item.EndDate)
  .OrderBy(rnd.Next())
  .Take(1);

Cheers,

/Dirk

Hi Bo

There are a few things missing from your problem description. I pinged you on Twitter, so we now know you are running 4.7.2 :)
Next thing, how many content items are we talking about? I played around with just 5 and haven't seen any performance issues ... :P

I was a bit confused about the contruction of your query.
I think I got it though, so I rewrote it to hopefully make it a bit more clear. Could you try it and see if the performance issues persists?

Random rnd = new Random();
var contest = contests.Children.Where("startDate <= DateTime.Now && endDate >= DateTime.Now").OrderBy(rnd.Next()).FirstOrDefault();

I've had a similar problem in this topic: http://our.umbraco.org/forum/developers/razor/28479-Razor-menu-performance-(v4). You might not like the solution, but that fixed it for me :-).

Jeroen

Hi guys,

Thanks for your replies :-)

I have tried to tinker around with the code you wrote, but either way it's still hangin' :-/ The load time on startDate property is up to: 0,886731 when having a look at the page with umbDebugShowTrace, and that's on localhost.

Got a few questions about what "contests" is. It's simply a DynamicNodeList which I get like this:

var contests = Model.AncestorOrSelf().Contests.Single();

@Jeroen, yeah.. I found your post in a search, but was hoping it had been fixed since :-/

Thanks again!

- Bo

There does indeed seem to be quite a performance penalty for using dynamic .Where, at least in 4.7.2.

Would it be possible for you to not run the query dynamic ?

It should be fixed in 4.10 if you use the new Views. Shannon rewrote the code and if you use the strongly typed examples it should be faster.

Jeroen

@Mads: yea, I'm working on a (nasty) hac... err.. solution to use Node instead :-)

@Jeroen: Oh, that's good news! But upgrading is not an option at the current state of the site I'm afraid :-/

Anyway, I'll post the code here if/when I come up with something that works.

Thanks again!

- Bo

Random rnd = new Random();
var contests = Current.AncestorOrSelf("Contests").GetChildrenAsList.Items;
var contest = contests.Where(x => DateTime.Parse(x.GetPropertyValue("startDate")) <= DateTime.Now && DateTime.Parse(x.GetPropertyValue("endDate")) >= DateTime.Now).OrderBy(x => rnd.Next()).FirstOrDefault();

Something like the above should do the trick ?

Thanks Mads! I'll try it out :-)

I just had a chance to try out my original code on the live site, Strange thing is that there's absolutely no performance hickups on the live site with my originally posted code. Doesn't make any sense to me, but as long as it works I guess everybody is happy ;-)

- Bo

is working on a reply...