We are using CMSImport v3.7.3 and Umbraco v7.5.13. In our website we have over 120 document types and around 6000 nodes in our content tree. When we try to import it takes a long time to hit any screen in the wizard.
We created a simple 1 record csv then tried to import, after selecting csv datasource then clicking next it took around 5mins to get to next screen when we could then pick document type and location to import to.
FYI the document type that we are trying to import to has 85 properties. When we click next on mapping screen that also takes a long time. Then clicking import it just spins and we cannot import.
I think the 85 properties on a single document type is causing the issue. CMSImport inspects every assigned property during import since it might need to convert data. That is also the case when selecting the mapping. Not sure how to fix that other than increasing timeouts. Is it really needed to have all 85 properties?
Refactor is not really an option. We are currently hitting the db with sql trace see if there is anything there to optimise. I am guessing you are using content service to get properties etc or are you making sql calls directly?
On thing we noticed after putting on sql trace is that after selecting our document type and clicking next instead of just getting properties for that document type it seems to be getting all properties of all document types and not just properties of selected one.
Indeed the whole structure will be read as once. I was assuming this was cached which wasn't . In the version below the structure is cached so only processed once https://www.dropbox.com/s/vyw7rtodmj85a6i/cmsimport37_5.zip?dl=0
But still with that amount of properties on a doctype I don't think performance will be great during import.
Performance issue
Hello,
We are using CMSImport v3.7.3 and Umbraco v7.5.13. In our website we have over 120 document types and around 6000 nodes in our content tree. When we try to import it takes a long time to hit any screen in the wizard.
We created a simple 1 record csv then tried to import, after selecting csv datasource then clicking next it took around 5mins to get to next screen when we could then pick document type and location to import to.
FYI the document type that we are trying to import to has 85 properties. When we click next on mapping screen that also takes a long time. Then clicking import it just spins and we cannot import.
Any ideas / suggestions?
Regards
Ismail
Hi Ismail,
I think the 85 properties on a single document type is causing the issue. CMSImport inspects every assigned property during import since it might need to convert data. That is also the case when selecting the mapping. Not sure how to fix that other than increasing timeouts. Is it really needed to have all 85 properties?
Best,
Richard
Richard,
Refactor is not really an option. We are currently hitting the db with sql trace see if there is anything there to optimise. I am guessing you are using content service to get properties etc or are you making sql calls directly?
Regards
Ismail
Hi Ismail,
Yes using the content service indeed.
Best,
Richard
Richard,
On thing we noticed after putting on sql trace is that after selecting our document type and clicking next instead of just getting properties for that document type it seems to be getting all properties of all document types and not just properties of selected one.
Just to get to mapping screen is taking 13mins.
This in an i7 machine with 16gb ram.
Regards
Ismail
That's weird indeed will add that to the list to check, normally not a big issue but in your case I can imagine that it gives some issues.
We just installed on a smaller site with 15 document types and it took 2 mins to get to the mapping page for a document type with 16 properties.
Regards
Ismail
HI Ismail,
Indeed the whole structure will be read as once. I was assuming this was cached which wasn't . In the version below the structure is cached so only processed once https://www.dropbox.com/s/vyw7rtodmj85a6i/cmsimport37_5.zip?dl=0
But still with that amount of properties on a doctype I don't think performance will be great during import.
Hope this helps a bit,
Richard
Richard,
Brilliant that is alot better so mapping is very quick. Import is around 50 seconds.
We will test a bit more with client but its looking alot better.
Many thanks Richard.
Regards
Ismail
Great to hear
is working on a reply...