Performance Is Slow

Diagnose and fix slow canvas loading, long transaction load times, and timeouts.

Symptom

  • The canvas takes a long time to display objects.
  • A transaction takes many minutes to load.
  • The browser shows a timeout or connection error.
  • CAST Imaging becomes slow after an application with many objects is imported.

Step 1: Check Neo4j memory

Insufficient Neo4j memory is the most common cause of slow performance.

See Manage Neo4j — Optimize memory allocation.

Step 2: Reduce the view size

Very large views (many objects and links) are slow by design. Try these options:

  • Use the Reduced call graph instead of Full. See Call graphs.
  • Use Focus to show only the selected object and its neighbours. See Focus on a subset of objects.
  • Use the Selective expand dialog at Level 5 instead of expanding all objects.

Step 3: Adjust the Full Call Graph notify threshold

If users often accidentally load very large Full Call Graphs, lower the threshold so they are prompted before loading.

See Configure display preferences.

Step 4: Tune import batch size and aggregation limits

See Monitor and tune performance.

Step 5: Enable SQL execution logging

Enable SQL logging to identify slow database queries that contribute to long load times.

See Monitor and tune performance — Enable SQL execution logging.