Hey were now using something in the system. Well kinda, mixed in with more usage of the above method.

In a tiny portion of application warm up 81.7% of time is spent in JIT overhead; now we can pretty much ignore that (kinda) as we know profilers disable native imaging which means the system will have to jump to JIT. Can't quite ignore the fucking horrendous pile of code it takes JUST to get a tiny bit of data.

In fairness, once started, with A LOT of the site not actually making use of umbraco it performs ok. The nodes being loaded in this instance was simply pulling the content of an advert container. Which consists of 3 adverts; an advert consisting of a dropdown (3 items in it to set the type), a media picker (1 image) and a url.

Bit of a double edged blade; if you use umbraco doctypes for everything (think blog style/comments/date filters/long trees lots of properties) it blows and flamethrows memory till there's nothing left; if you treat umbraco like a repository your reliant on the API being stable, set in stone, and eventually, and probably not as far away as you'd like it, to be able to debug it without being dropped into a mass of generic/anonymous methods/linq hell.