Replies: 1 comment 2 replies
-
@Luis-Art-Guerra : that's indeed quite long, not what I would expect. Might be that you're getting throttled? You can indeed split the templates in smaller parts, each doing one feature (e.g fields / lists / ....) or each doing one entity (e.g. doc lib 1 with all dependencies, then doc lib 2, ...) Would also be good if you could figure out which handler (lists, fields, ...) is so slow, feels that there's a performance improvement. If you find something please open an issue in the issue list for it |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
My current template takes more than 120 minutes to be applied to a new site.
It contains 15 Document LIbraries, each one with around 4 views and 53 field references.
Is it normal that it takes that amount of time?
We are currently using wsp templates and it takes around 10 min to create the whole site. However, these templates are no longer supported for Modern sites.
Aside from the problem that a process that took around 10 min now takes 2 hours, we are currently migrating all our processes to the cloud, and I'm not sure an azure function can last 2 hours executing: could be possible to divide the template in various sub-templates, each part taking care of a minimal task. For example: one template creates a library, another creates the views, other the fields references and another one the security. That way the whole process may take the 2 hours, but is divided in activities of around 5 minutes.
Beta Was this translation helpful? Give feedback.
All reactions