We are now over 100,000 nodes after letting our import process run for a while (on and off over several weeks), and I'm still wondering if there's any way to speed this up. I think a lot of the overhead (unnecessary database storage and round trips) when calling SaveAndPublish or SaveAndPublishWithStatus comes from versioning - is there a way to disable versioning, or is there any other solution for speeding up this process? It is taking 20-30 seconds for every call to SaveAndPublish(), even on existing nodes.
Disclaimer: I haven't tried that and you risk deleting important data.
I vaguely remember a somewhat recent blog about some tricks to improve Umbraco performance, and one of the tricks was to delete old versions of content. Can't seem to find the link though. You might try searching through the Umbraco RSS feed for the article.
Also, I agree that performance is abysmal (e.g., I submitted this similar issue: http://issues.umbraco.org/issue/U4-6042). I recommend you submit an issue to the Umbraco issue tracker to at least make to core team aware of your usage scenario and the problems you are encountering with performance.
ContentService performance, continued
We are now over 100,000 nodes after letting our import process run for a while (on and off over several weeks), and I'm still wondering if there's any way to speed this up. I think a lot of the overhead (unnecessary database storage and round trips) when calling SaveAndPublish or SaveAndPublishWithStatus comes from versioning - is there a way to disable versioning, or is there any other solution for speeding up this process? It is taking 20-30 seconds for every call to SaveAndPublish(), even on existing nodes.
You could delete old versions: https://our.umbraco.org/projects/developer-tools/sql-scripts
Disclaimer: I haven't tried that and you risk deleting important data.
I vaguely remember a somewhat recent blog about some tricks to improve Umbraco performance, and one of the tricks was to delete old versions of content. Can't seem to find the link though. You might try searching through the Umbraco RSS feed for the article.
Also, I agree that performance is abysmal (e.g., I submitted this similar issue: http://issues.umbraco.org/issue/U4-6042). I recommend you submit an issue to the Umbraco issue tracker to at least make to core team aware of your usage scenario and the problems you are encountering with performance.
is working on a reply...