Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Saif Obeidat 53 posts 200 karma points
    Aug 24, 2019 @ 11:02
    Saif Obeidat
    0

    Saving and publishing the website root takes a long time to finish - Umbraco 8

    Hi all,

    I have tried to save and publish the website's root and it took about 10 minutes to finish..

    my website's structure is :

    Root (home)
    -- News
    ---- Category1
    ------- News 0001
    ------- News 0002
    ------- .........
    ------- .........
    ------- News 3000

    ---- Category2
    ------- News 0001
    ------- News 0002
    ------- .........
    ------- News 3000

    my website is on the same server as the website and my hard drive is SSD.

    Why is that happening ? and how to resolve it ?

  • Shaishav Karnani from digitallymedia.com 330 posts 1562 karma points
    Aug 24, 2019 @ 13:48
    Shaishav Karnani from digitallymedia.com
    0

    We have been running Umbraco 8 and it is quick even publishing the root node. So, something is wrong with the setup.

    Few points to check:- 1) Have you added any additional packages or code on top of it? 2) Can you also make root of your site to have read/write permission?

    Regards, Shaishav

  • SteveV 42 posts 202 karma points
    Aug 24, 2019 @ 18:38
    SteveV
    0

    How many pages do you have and what are the specs of the server?

  • Saif Obeidat 53 posts 200 karma points
    Aug 24, 2019 @ 18:51
    Saif Obeidat
    0

    Hi SteveV,

    I have around 8000 nodes.. and going to have more.

    the project is in my computer for now, and the main specs of it are :

    Intel Core i7-7700
    Ram 24GB
    500GB SSD

  • Nadia 2 posts 74 karma points
    Aug 25, 2019 @ 06:47
    Nadia
    0

    Hello, I have the same problem as Saif. I have a node with thousands of documents and when I save the node or the parent of it I wait a long time. I think the framework should only save the updated node. I had to create a configuration node unrelated to the home because it is impossible to wait so long.

    Regards, Nadia

  • SteveV 42 posts 202 karma points
    Sep 04, 2019 @ 22:46
    SteveV
    1

    I'm able to replicate your issue. It seems that after the document is updated a query is executed on the database that selects the updated node and all it's descendants, probably to rebuild the cache. I analyzed the query in SSMS and it recommended to add 2 indexes:

    CREATE NONCLUSTERED INDEX TEST_IX_umbracoContentVersion_nodeId ON dbo.umbracoContentVersion (nodeId)
    CREATE NONCLUSTERED INDEX TEST_IX_umbracoNode_nodeObjectType_trashed ON dbo.umbracoNode (nodeObjectType,trashed) INCLUDE (uniqueId,parentId,[level],[path],sortOrder,nodeUser,createDate)
    

    In the end the duration of the query will still be dependent on the amount of descending nodes you have but these 2 indexes should give it a serious performance boost.

    To remove the indexes:

    DROP INDEX TEST_IX_umbracoContentVersion_nodeId ON dbo.umbracoContentVersion
    DROP INDEX TEST_IX_umbracoNode_nodeObjectType_trashed ON dbo.umbracoNode
    

    I'll try to create an issue and/or pull request later on Github.

  • Saif Obeidat 53 posts 200 karma points
    Sep 23, 2019 @ 07:30
    Saif Obeidat
    0

    Hi Steve,

    I will try your solution, by the way, did you create an issue for this one?

  • SteveV 42 posts 202 karma points
    Sep 23, 2019 @ 21:20
  • SteveV 42 posts 202 karma points
    Oct 15, 2019 @ 10:24
    SteveV
    0

    Version 8.2.0 has been released. This update should fix the slowness. Don't forget to remove the indexes in my previous post before applying the update.

  • Saif Obeidat 53 posts 200 karma points
    Oct 16, 2019 @ 06:27
    Saif Obeidat
    0

    Yes I tested the new version and it works perfect.

  • Nadia 2 posts 74 karma points
    Sep 05, 2019 @ 07:06
    Nadia
    2

    Thanks Steve, I tried your suggestion and it's faster. I think the cache should only be rebuilt for all child nodes if I update the navigation properties or other dependent properties. In my case I have created a custom document type which, over time, will contain thousands of documents. Usually the Home has a fixed url and does not change (url host). The rebuild of all child nodes could be limited. It is just an idea to confront.

    best regards Nadia

Please Sign in or register to post replies

Write your reply to:

Draft