An operator has noticed that the Avi GUI is very slow. Which reason explains this slowness?

Question

Options

• ALog all headers and Non-significant logs options have been enabled for multiple busy VSS.
• BCompression has been enabled for multiple busy VSs.
• CTwo different clouds have been configured in this Avi Controller.
• DCaching has been enabled for multiple busy VSs.

• A
  4% (1)
• B
  83% (20)
• C
  4% (1)
• D
  8% (2)

Explanation

Enabling compression on multiple busy Virtual Services (VSs) places heavy CPU load on the Avi Controller, not just the Service Engines. The Controller must handle compression-related analytics, decompression for deep inspection, and metric aggregation for all those VSs simultaneously - this resource contention directly degrades GUI responsiveness.

Why the distractors are wrong:

• A - Verbose logging (all headers + non-significant logs) increases log volume and disk I/O, but is not the primary driver of GUI slowness; it mainly affects log storage and retrieval.
• C - Having two clouds configured is a supported, standard topology and carries no inherent performance penalty on the Controller GUI.
• D - Caching reduces backend load and response times; it is a performance optimization, not a cause of slowness.

Memory tip: Remember "Compression ≠ free on the Controller." While Service Engines handle the actual traffic compression, the Controller still must process and aggregate all the resulting analytics for every compressed response across every busy VS - multiply that across many VSs under load and the Controller's CPU becomes the bottleneck.

No community discussion yet for this question.