Using Umbraco 7.3.3, Ditto 0.8.3 and Dittol ModelFactory 0.1.1. I have the following:
Stations doctype - model class Stations
Station doctype - model class Station.
Station is child of Stations and we have 2.7k of them. So when i load the Stations page it takes 14 seconds. If i take out the code in OnApplicationStarting for ModelFactory namely:
var types = PluginManager.Current.ResolveTypes<PublishedContentModel>();
var factory = new DittoPublishedContentModelFactory(types);
PublishedContentModelFactoryResolver.Current.SetFactory(factory);
Then its all a lot quicker. On my stations model I do not have Children property. So could it be that the children are being loaded up?
Just replied on the GitHub issue too, (no doubt you'll have an email notification already) :-)
The large number of child nodes are definitely the bottleneck issue with Ditto ModelFactory. Marking the Stations property with virtual will enable the lazy-loading feature.
Bit confused Stations property? I don't have stations property I have stations class that has station children 2.7k of them. On the stations class i did try creating Children property and marking that virtual thinking it would over ride the default Children property?
Anyhow for now we have taken out ModelFactory and performance is much better.
I was making a guess at the property name... but something on the model (or page) is making a call to the content node's Children... which is why ModelFactory would be being hammered.
Anyway, cool for taking Ditto ModelFactory out of the equation, I find it pretty difficult to offer community support for it - there's too many moving parts.
Ditto performance
Guys,
Using Umbraco 7.3.3, Ditto 0.8.3 and Dittol ModelFactory 0.1.1. I have the following:
Stations doctype - model class Stations Station doctype - model class Station.
Station is child of Stations and we have 2.7k of them. So when i load the Stations page it takes 14 seconds. If i take out the code in OnApplicationStarting for ModelFactory namely:
Then its all a lot quicker. On my stations model I do not have Children property. So could it be that the children are being loaded up?
Has anyone else seen this?
Regards
Ismail
Not a solution but I have now taken out ModelFactory and am using standard .As extension method all runs alot quicker.
Regards
Ismail
Hi Ismail,
Just replied on the GitHub issue too, (no doubt you'll have an email notification already) :-)
The large number of child nodes are definitely the bottleneck issue with Ditto ModelFactory. Marking the
Stationsproperty withvirtualwill enable the lazy-loading feature.Cheers,
- Lee
Lee,
Bit confused Stations property? I don't have stations property I have stations class that has station children 2.7k of them. On the stations class i did try creating Children property and marking that virtual thinking it would over ride the default Children property?
Anyhow for now we have taken out ModelFactory and performance is much better.
Regards
Ismail
I was making a guess at the property name... but something on the model (or page) is making a call to the content node's Children... which is why ModelFactory would be being hammered.
Anyway, cool for taking Ditto ModelFactory out of the equation, I find it pretty difficult to offer community support for it - there's too many moving parts.
is working on a reply...