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?
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.
@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.
Hi @kgroneman - did you ever get any additional insight on this from someone at Khoros? I am also wondering the same.
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.
No, no customizations on that page.
My main question remains:does the number of nodes affect the performance?