Node limits and performance considerations

Node limits and performance

Certorix does not enforce hard limits on node counts, but there are practical performance considerations.

Recommended maximums

• Nodes per tree – Up to 200 nodes for smooth canvas editing. Beyond 200, canvas panning and zooming may become laggy.
• Answers per Question node – Up to 10 answers. More than 10 may overwhelm customers. Use Input node or Condition node for many options.
• Tree depth – Up to 50 sequential nodes before reaching a Solution. Customers rarely complete more than 20 steps.
• Embedded images in Info nodes – Images under 500 KB recommended. Large images increase widget loading time.
• Total trees per organization – No limit (only published trees count toward plan limit).
• Total facts per organization – No limit (only certified facts count toward plan limit).

Performance impact of large trees

• Editor loading time – Trees with 500+ nodes may take 5‑10 seconds to load the canvas.
• Widget loading time – The widget loads the entire tree structure. Larger trees = slower initial load for customers.
• Auto‑save latency – Very large trees (1000+ nodes) may have noticeable delay (1‑2 seconds) after each edit before auto‑save completes.
• Browser memory – Complex trees with many nodes consume more browser memory, potentially causing slowdowns on lower‑end devices.

Best practices for large diagnostic flows

• Split into multiple trees using Jump nodes – Instead of one 500‑node tree, create five 100‑node trees connected by Jumps.
• Use Condition nodes to skip irrelevant branches – Reduces the number of nodes customers actually traverse.
• Archive old trees – Instead of deleting, unpublish and archive (move to a folder or tag as 'archived').
• Export large trees for backup – Regularly export large trees as JSON for safety.

When to contact support about limits

If your tree exceeds 1000 nodes or you have legitimate performance issues, contact support. We may increase limits for Enterprise customers.