Number of nodes vs performance?

[kgroneman]

On our site,  we've been saving archives for years.   After all, someone MAY need some of that data someday.   We have many more archived nodes than we do public.   My question is:  Does the number of nodes influence site performance (community/admin/studio)?  Are there any other negative impacts from saving all data from just shortly after the dinosaurs became extinct forward?  

 - Kim

[lilim]

Hi Kim,

We have hundreds and hundreds of nodes in our 15 year old community.

It definitely affects how long the Community Structure takes to load in the admin console (even with the new lazy load). However, we have not noticed any other performance issues in regards to this.

[kgroneman]

@lilim Thanks.  Yea, community structure takes a long time, but not quite as long as it used to with the segmented (lazy) load.   I was just wondering if I'd get lightning speed on the normal nodes if I removed some of the baggage.  Sometimes it takes 4 or 5 seconds to render a forum reply page etc. 

[lilim]

Hi @kgroneman - did you ever get any additional insight on this from someone at Khoros? I am also wondering the same.

[kgroneman]

@lilim Nope..  I didn't ask Khoros.  I just took your word for it. 🙂

[lolagoetz]

Do you have any customizations on the reply page? That sounds like a latency issue that doesn't really need to touch structure, but it's hard to tell without more detail.

If your reply page is taking that long to load, I would have someone monitor it to see what the laggard actually is. And then potentially file a support case if you can't find it.

[kgroneman]

No, no customizations on that page. 

[lolagoetz]

And not the newest version of the RTE either, right?

[kgroneman]

My main question remains:does the number of nodes affect the performance?

[lolagoetz]

Gotcha. I was trying to zoom in on the reply load issue.

@akshayraghoji @tsrisudh  have you noticed any problems on Cisco's site considering how many nodes you have had in the past?

[tsrisudh]

We have quite a few nodes, but we see that it does not have a bearing on the overall performance of the application.

[kgroneman]

Just to update this issue with additional information related to number of nodes and performance.   It does. 

 We have a "fly out" hamburger menu that lists the categories and you can drill down in nodes.   When we updated to 19.7 a while back, items on that menu disappeared for some users.   I opened a case with Khoros and they say there's a 1000 node limit for some things like a menu to work.   Well we had over 600 nodes in our archive. so people with rights to see the archive would have a broken menu.  Khoros is working on a fix.  I don't think anyone knows what other impact going over that 1000 node limit has.