I would like to know if anyone have experience with large documents in umbraco. I have a site with 50+ properties in one of the document types.
This causes this type of documents to take 8-10 seconds and a lot longer to save/publish. All other documents loads quite fast. There is nothing special about the document type other than the high number of properties.
Running the SQL Server Profiler with default settings reveals 4000 rows of activity (~1000 queries) when loading a document of this type in umbraco.
The frontend is performing quite fine. It is just the umbraco backend that's slow.
How many properties should I be able to have in a document type without any problems?
I had doc type with around 40+ properties and this was on old v4 beta, the only issue i had was sorting of properties on one of the tabs i had around 30 other than that it worked fine.
Niels : There is no PRO subscription with the project, unfortunately.
Daniel : I have some custom data types in this document type, but the heavy database activity is initiated by umbraco, not by data types.
Ismail : I only have 15 properties on the tab with most properties, so sorting hasn't been a problem for me. I haven't had problems sorting properties in v4. In v3 it was a pain :-)
I guess I will do some more debugging. I can't figure out what causes the problems. All other document types are performing fine. I will try the export the SQL Profiler output and post the here on the forum as soon as I get back to the office. Perhaps you can see if everything looks fine or if the DB activity is abnormal.
Some ideas for debugging: Export the document type and importing it into a clean install (maybe editing out the custom data types first, or better create the custom data types there as well) to see if it performs equally bad there? Or re-importing it under a new name in the same install and testing that doctype? Maybe even post the UDT here so for others to test?
I have looked closer to the database activity, and it all seemed legitimate. For each property I removed from the doc type the amount of database activity was reduced a relative equal amount.
However - the database I was running was running in Full Backup mode. I changed this to Simple, and it if not solved then at least took off some of the heat on the performance issue. Documents based on this document type does now load in 1-2 seconds and save in 5-6 seconds. It's quite a difference from before.
Now I just hope I wont be needing any point in time restore of the database in the future ;)
Experience with large documents? (50+ properties)
I would like to know if anyone have experience with large documents in umbraco. I have a site with 50+ properties in one of the document types.
This causes this type of documents to take 8-10 seconds and a lot longer to save/publish. All other documents loads quite fast. There is nothing special about the document type other than the high number of properties.
Running the SQL Server Profiler with default settings reveals 4000 rows of activity (~1000 queries) when loading a document of this type in umbraco.
The frontend is performing quite fine. It is just the umbraco backend that's slow.
How many properties should I be able to have in a document type without any problems?
That sounds like (way) to many requests. Are you running v3 or v4?
4.0.1 upgraded from a clean 4.0.0
Do you have any properties with custom datatypes that handles its own db stuff, that could be the cause of all that db activity?
I have worked with documents with 30+ properties several times and have not experienced that much of a performance hit.
That sounds odd. If you have a PRO account with the project let me know and I'll look into it.
milandt,
I had doc type with around 40+ properties and this was on old v4 beta, the only issue i had was sorting of properties on one of the tabs i had around 30 other than that it worked fine.
Regards
Ismail
Niels : There is no PRO subscription with the project, unfortunately.
Daniel : I have some custom data types in this document type, but the heavy database activity is initiated by umbraco, not by data types.
Ismail : I only have 15 properties on the tab with most properties, so sorting hasn't been a problem for me. I haven't had problems sorting properties in v4. In v3 it was a pain :-)
I guess I will do some more debugging. I can't figure out what causes the problems. All other document types are performing fine. I will try the export the SQL Profiler output and post the here on the forum as soon as I get back to the office. Perhaps you can see if everything looks fine or if the DB activity is abnormal.
Some ideas for debugging: Export the document type and importing it into a clean install (maybe editing out the custom data types first, or better create the custom data types there as well) to see if it performs equally bad there? Or re-importing it under a new name in the same install and testing that doctype? Maybe even post the UDT here so for others to test?
Good luck!
I can't really seem to find any cause of the problem. I have tried removing my custom data types but still the same.
If anyone can see anything that should cause problems from the udt, please let me know.
[code]
[/code]
I have looked closer to the database activity, and it all seemed legitimate. For each property I removed from the doc type the amount of database activity was reduced a relative equal amount.
However - the database I was running was running in Full Backup mode. I changed this to Simple, and it if not solved then at least took off some of the heat on the performance issue. Documents based on this document type does now load in 1-2 seconds and save in 5-6 seconds. It's quite a difference from before.
Now I just hope I wont be needing any point in time restore of the database in the future ;)
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.